Pixel Crushers Forum

Great, I'm glad to hear that this is not pure madness to do this : ) About the grain of salt ;) , I'm not sure, but I'd rather say that we should check that the Dialogue Manager's Reevaluate Links After Subtitle is also UN ticked when deciding to not evaluate links , no? If we don't evaluate links t...

Hi Tony, I read somewhere that you had the Covid, I hope you're recovering well! I've dug a little deeper into this story of look-ahead thing. Because I don't really need it in my project and mostly because it can provoke some inconsistencies between articy and the dialogue system (with all instruct...

Thank you, that would be awesome!

I'm on the 2.2.46.1 version. I tested your package and can confirm what you say, the order is respected if the instruction is in a regular node (non-group). And I agree about the fact that depending on the situation, it's crucial that groups run their scripts during this look-ahead step. To go back ...

I believe the alert is only shown at the end because alerts are not allowed during conversations... If I allow it, the alert is shown just before the 2nd dialogue line. Do you have any idea about a way to avoid this kind of situation, without having to add extra regular nodes before all scripts? May...

Hi Tony! Thank you for the feedback. I agree that the Alert message is shown after the 2 dialogue lines by the UI, that is ok. But strangely the debug messages seem to confirm that the lua script is executed before the 2nd line is spoken and before its delay: ScriptOrder1.png Is it the same for you?...

Hi Tony,

Any news about this? Does it also happen on your side...?

Have a good week!

Perfect, thank you for the explanation & the future fix!

Hi Tony, During conversations, I can see that the OnConversationStart message is sent just after the first OnConversationLine message. I guess this is normal behavior, looking at the StartConversation method of the DialogueSystemController script, the method: m_conversationController.Initialize(mode...

Even with the Reevaluate option ticked, if I Iook at the Dialogue System debug info, it looks like the 3rd group node (and its instruction) is still evaluated before the 2nd dialogue node is spoken.