A couple of lines are spoken and then it fades to black, delays for a second and then fades back in and continues to the next
node. I found that through testing that I was able to press the continue button mid fade which would progress to the next node, thus leaving the screen black. So I put in the SetContinueMode(false) and then at the end of the last fade I send a message and when that mesage is sent I set the continue mode back to true and Continue().
Problem is that when I set it to SetContinueMode(false); it is progressing past the node thta has it and continues through until it reaches the last node in the conversation. Whats even more odd is that I see the continue button being disabled on the SetContinueMode(false) node, but it is being enabled almost immediately.
I even made a blank conversation with 3 nodes and put the SetContinueMode(false) on the second node. IT does the same thing. Turns of then back on the continue button and steps through the rest of the conversation.
This is what I am trying to do. Also the odd thing is that I do this in other levels in other conversations but it is only happening in this level and any new conversation. I also took the continue button out of the Dialogue UI Panels button slot but I still see it being disabled at that node call. What else has access to that button. Dialogue Manager?
Code: Select all
SetContinueMode(false)->Message(Stop);
Fade(stay, .75)@Message(Stop)->Message(Sleep);
Delay(2)@Message(Sleep)->Message(Wake);
Fade(in, .75)@Message(Wake)->Message(Fin);
SetContinueMode(true)@Message(Fin)->Message(Go);
Continue()@Message(Go);