Thanks for the fast reply.
Wait, Is this “*” the thing I wanted “above”?
Forces transition to the next node
Seems exactly what I was looking for. But I tried this in a decision and it didn’t work.
How to use that?
Thanks
Thanks for the fast reply.
Wait, Is this “*” the thing I wanted “above”?
Forces transition to the next node
Seems exactly what I was looking for. But I tried this in a decision and it didn’t work.
How to use that?
Thanks
Hi @info_AM and @K3
I’ve been away but coming back to this thread.
The “*” wildcard was exactly what I was referring to but this does not work for me. @K3 Can you provide an example of how this can be used?
Thanks, so much.
Yes, I followed your advice / info. But I couldn’t get it working. Therefore I tried other solutions like “speach start and end” as a trigger to move to the next section. But this causes long delays.
My next test is to have all “introduction text” said in one section. But to have this in a nice manner I need pauses. Opened another question here: Pause / delay in a given text
The “*” still requires user input to proceed.
To use it correctly, you need to place “*” in the Decision.
In the example I shared in the screenshot:
When you activate a Section using a Trigger, a new response is generated, which naturally causes a delay, just like asking a question and waiting for a reply.
If user input isn’t required and you just need the character to deliver a fixed message, wouldn’t it be more efficient to use a TTS service directly?
But I still want the text in the convai text ui element. Is that possible? I mean I want to use convai and the LLM / GPT in the experience. Just the start needs to be a bit scripted and I want to highlight elements along the way (text). That’s why I tried to have multiple sections. To have individual triggers to show/hide gameobjects.
And, same as @Nick_Clarke mentions. The force should be possible without user-input ![]()
Ideally, I’d love to see the “*” in the decision force the transition to the next section without the need for user input. That would be pretty powerful.
As I mentioned in my previous messages, I’ve shared this as feedback with our team.
For now, the only solution is to use Triggers.
@K3 , thanks, I’ll work with that and keep an eye out for any changes.
Thanks for looking into this.