Conversation stuck in start state when triggering through timeline

[urrmurrmur]

Hi,

I'm confronted with strange behavior that I cannot figure out. I have a conversation which I am starting through a timeline Cinemachine track. However, when doing so, the conversation gets stuck in the start state and never continues to the first actual conversation state. If I create a new test conversation and trigger that one from the exact same timeline, it starts as expected.

I've run the unique id tool a while ago and that broke a bunch of my conversations. My current working theory is that this is the cause of the issue, but I don't know why or in what way.

This is my conversation, with start state.

dsfu_0812_1.png (68.92 KiB) Viewed 623 times

The timeline that I'm starting the conversation from:

dsfu_0812_2.png (22.34 KiB) Viewed 623 times

The inspector for the start conversation item on the track:

dsfu_0812_3.png (36.11 KiB) Viewed 623 times

And this is the test conversation that does work. All I'm doing is changing the triggered conversation in the timeline to this one.

dsfu_0812_4.png (55.74 KiB) Viewed 623 times

I'm honestly not seeing what's different about this one, unless something has gone fubar behind the scenes when I ran the unique id tool. Btw, I have tried changing the actor of the start state in the no-functional conversation to Arne after taking the screenshots, but that makes no difference.

Any ideas what may be going wrong?

[Tony Li]

Hi,

It looks like you may have at some point clicked the <START> node's "I understand. Edit anyway." button and cleared its Sequence field. To fix it, click "I understand. Edit anyway." again and set the Sequence field to: None()

[urrmurrmur]

Huh, weird. I can't image when or why I would have done that. But that was indeed the problem.

Thanks, Tony.

[Tony Li]

I'm glad it's working now.

[urrmurrmur]

Tony, in case this is of any value to you: I have a different conversation where the start node is also missing its "None()" sequence. For that one I am 100% sure that I did not alter it myself, even accidentally, so something else must have caused this. I still suspect the unique id tool is related in some way.

Not a huge deal, but it may help you track down a small bug in the future.

[Tony Li]

Hi,

I don't think it's the Unique ID Tool, as that doesn't touch the Sequence field, but it could be something else. The Unique ID Tool only changes dialogue database internal IDs to ensure they're unique across the selection of databases that you've specified, and there are no known issues with that process. If you do find some operation or utility that causes the issue, please let me know.