Pixel Crushers Forum

Hi,

I have a conversation written that is triggered by OnTriggerEnter. It is a 'class change' dialogue and the player is meant to be able to replay the conversation as much as they wish in order to change classes.

The initial invocation of the conversation works fine--the entire conversation plays. However, on the second and subsequent conversations, only the first node of the conversation plays and then immediately skips the rest of the conversation, exiting immediately.

After some testing, I found out that this affected all of my conversations; not just this dialogue.

How can I get all my conversations to replay more than their first node?

Hi,

Temporarily set the Dialogue Manager's Other Settings > Debug Level to Info. (See this tutorial for details.)

The reproduce the issue in the Unity editor's play mode. This will let you trace through the Console window to see why the conversation is exiting early.

If I trace the flow of one of my dialogues in the Conversations view, this is what I see.

On the first invocation


On the second and subsequent invocations


If I'm understanding correctly, on the second invocation the links are not being added? Why is that the case?

Hi,

I have no idea.

Try assigning an actor to the conversation's Actor dropdown. (Menu > Conversation Properties.)

Please feel free to send a reproduction project or a copy of that database to tony (at) pixelcrushers.com. I'll be happy to take a direct look.

Okay, I sent you a copy of my dialogue database. I tried assigning an actor but it doesn't seem to have changed anything.

I do notice that for some reason, there's an Add Link instruction that differs between the first and subsequent conversations. Maybe that's relevant?

Hi,

Thanks for sending a copy of the database. I replied to your email. I will need a bit more info.

Sent you a reproduction project.

According to Tony, there was a bug related to an outdated Ink Integration package. After updating the package, my issue was resolved.

Thanks Tony!

Glad to help! And thanks for updating the thread here. If someone else encounters the same issue, it will be very helpful.