Pixel Crushers Forum

I swear this used to work correctly, but now when I call LoadLevel, it keeps the conversation open in the next scene. I've made a gif of it here: Since I've done a LoadLevel, I would assume that the previous conversation should end, but it's not.

Here's my log:



Here's my conversation:

Nope, LoadLevel() doesn't stop the conversation. This allows a conversation to span multiple scenes.

Ah, OK, that's good to know. But even though that's the case, I don't understand why the scene wouldn't end: That's the last node, it has no text, and its sequence is "LoadLevel(IntroNewBedroom)". Shouldn't that just pass through and end the conversation? Plus it still says it's on the node above. Is it not ending because it's running the Default Sequence which is "Delay({{end}})"? I assumed that if I didn't default (i.e., explicitly execute LoadLevel instead), the Default Sequence wouldn't run.

Regardless, changing that last node's sequence to "LoadLevel(IntroNewBedroom);Continue()" fixed the issue. Let me know if there's a better way to do that.

Update: I think I get it now. Somewhere I probably have a setting that says, "You gotta click continue." Since nobody clicked continue on that last node, it didn't go to the next step and end. That said, I'm still confused as to why the node above is colored green if it's executing the one below.

Your Dialogue Manager's Subtitle Settings > Continue Button dropdown is probably set to a mode that requires a continue button click. But, if I recall correctly, that's exactly what you want to happen in your conversations. Using the Continue() command on the last node like you did is the answer. The previous node may still be green because that's the node that last showed subtitle text.

Tony Li wrote: ↑Mon May 27, 2019 10:31 pm The previous node may still be green because that's the node that last showed subtitle text.

Ah. Out of curiosity, why not make the green one the currently executing node instead?

I think it actually should be. I'll confess that I was taking a guess because I'm finishing up for the night and didn't dig into the code to confirm or try to reproduce the issue. I'll try to take a look tomorrow.

K, thanks a lot. This isn't urgent at all to me because you helped me unblock the issue.