Pixel Crushers Forum

I put this in a Unity Package

[removed]

Thanks; I downloaded it, and I'm looking at it now. I removed the download link since it contains Dialogue System source files.

I can reproduce the issue. I'll post a fix here by this evening.

Thanks for alerting me to this timing issue. It involves sequences of the form "->Message(X); Continue()@Message(X)". This patch should fix it:

DialogueSystem_2_2_4_Patch20200106.unitypackage

Tony Li wrote: ↑Mon Jan 06, 2020 8:28 pm Thanks for alerting me to this timing issue. It involves sequences of the form "->Message(X); Continue()@Message(X)". This patch should fix it:

DialogueSystem_2_2_4_Patch20200106.unitypackage

Hi Tony, thanks for the patch. It fixed the case where two nodes have different parameter for Message(x).

This works now after the patch

Node1 Sequence:
MoveTo(destination, target, 1)@Message(1);
Continue()@Message(1);

Node2 Sequence:
MoveTo(destination, target, 1)@Message(2);
Continue()@Message(2);
-----------------------------------------------------

This doesn't work, node2 won't continue:

Node1 Sequence:
MoveTo(destination, target, 1)@Message(1);
Continue()@Message(1);

Node2 Sequence:
MoveTo(destination, target, 1)@Message(1);
Continue()@Message(1);

I'll check that and get back to you.

It was a timing issue. The sequencer activated the new command in the same frame that the previous node's command sent the message, so the new command also intercepted the message but too early. This patch should fix it:

DS_SequencerMessagePatch_2020-01-07.unitypackage

Hi Tony, the patch fixed the issues. Thanks for the help!

Glad to help! The fix will be in the next full release, too.