Sequencer message not received if used a second time?

[Abelius]

Hi there,

I'm having a problem with a conversation... this node, specifically:




The first time I run this conversation, the message is received from a PlayMaker FSM that uses the Send Sequencer Message action, then disables itself (the FSM). The node "receives" the message and jumps to the next node. All good.

Then, if I come back for a second time to the scene where this conversation is triggered, everything happens again (same conversation and same FSM which sends the message), but the conversation doesn't continue, as if the message is never received.

I wanted to eliminate the PlayMaker FSM as a problem, so I've set a breakpoint in the action code, but both times the line to actually send the message is run correctly:


First


Second

However, the conversation never advances the second time, as if the Sequencer never receives the message, or just ignores it.

I even added a delay at the start of the conversation to make sure there wasn't any racing condition, to no avail.

Any hints?

Edit: I can't see any mention to sequencer messages being sent or received, even at "Info" debug level. Is that expected?

[Tony Li]

Hi,

The Dialogue System's logging doesn't print out message sent/received messages.

I believe you're locked on DS version 2.2.15 for now, so the best approach will be if you can send a reproduction project to tony (at) pixelcrushers.com.

[Abelius]

Geezus, you have an amazing memory. xD

Yeah, I can't easily upgrade because I modified some scripts (PM actions, I think) and I don't remember which.

But is this fixed in a more modern version, you mean?

Anyway, I'll try to upload the thing with some instructions. Do you want me to delete the library folder before uploading? I think it'll take a while rebuilding it...

[Tony Li]

Hi,

Don't credit my memory; your signature says DS 2.2.15.

If you only modified PM actions, updating the core Dialogue System asset won't overwrite them. However, importing the PlayMaker Support package included in the Third Party Support folder would overwrite them. I don't know that updating to 2.2.32 would automatically fix the problem, but there have been changes and improvements to the sequencer system.

To make a reproduction bundle, zip up the Assets, Packages, and ProjectSettings folders. Those are the only 3 folders I'll need. You'll need to use a file sharing service such as Google Drive, Dropbox, or WeTransfer because it will be too big to attach to an email. In your email, please include the steps I should follow to reproduce the issue, what I should see when it works correctly, and what I will currently see.

[Tony Li]

Thanks for sending the repro project. I replied to your email with a solution. The issue appears to be that your FSM could sometimes send the sequencer message before the other sequencer commands start listening for it.