Typewriter sound during SetDialoguePanel(false)

[hipsterdufus]

Hi Tony, I put some pauses in my dialogues by using the sequencer commands like this:

required SetDialoguePanel(false);
required SetDialoguePanel(true)@3;

It works, but when the panel hides I am hearing the typewriter effect as the panel is closing. The typewriter effect is starting even though the panel is hiding just as the node is entered. Is there any way around this with the sequencer?

[Tony Li]

Hi,

The typewriter won't start if there's no text. Does the entry with SetDialoguePanel(false) have any Dialogue Text? If so, can you move SetDialoguePanel(false) to a prior node without text?

[hipsterdufus]

I moved the SetDialoguePanel(false) to the previous node and added an @Message(never) so it executes at the end of the node but there is still a typewriter effect (although it's not as long). I think it starts typing but stops when the hide animation is complete.

I can solve it by creating a blank node with these commands:
SetDialoguePanel(false);
Continue()@2;

Is there a better way though? Otherwise I'll have to put a lot of these blank nodes everywhere.

Secondary question - is there a way to disable the continue button during these pauses?

[Tony Li]

Hi,

Use the SetContinueMode() sequencer command to disable the continue button.

At what point does the typewriter erroneously play? When the blank node starts?

Can you post reproduction steps or send a reproduction project to tony (at) pixelcrushers.com?

[hipsterdufus]

The blank node method works fine I'd just like to avoid it if possible since it would add a lot of clutter. The typewriter sound briefly happens if I put the SetDialoguePanel(false)@Message(never) in the previous node. It will start to close the panel, and start typing the next node content. Maybe I can write a custom command to disable the typewriter effect or maybe there's a generic sequencer command to disable components?

[Tony Li]

There is a general-purpose SetEnabled() sequencer command.

Does the next node have text content? If so, perhaps it would be best to wait on the previous node until SetDialoguePanel(false) has finished. For example, if it takes 0.4 seconds for SetDialoguePanel(false) to fade out and deactivate the panel, you could do something like:

Code: Select all

SetDialoguePanel(false)@{{end}}; // After text duration, hide dialogue UI, which takes 0.4 seconds.
Delay(0.5)@{{end}} // After text duration, wait 0.5 seconds to allow dialogue UI to hide & deactivate.

[hipsterdufus]

I think I'll just have to put "wait" nodes. I couldn't quite get things to work using messages at the end of nodes and at the beginning - for some reason the continue functionality would get stuck when I turned it off and on again. I got the empty wait notes to work fine though. Actually having the empty wait nodes is easier to read on the diagram than having the sequence code buried within the conversation nodes. I suppose it would be nice if we could define our own custom node templates or comment nodes so that it's even more clear. Right now it just shows up as <> in the diagram window but it's not a big deal.

[Tony Li]

If a node's Dialogue Text is blank, the Title will appear inside <>. If you set the Title to "Wait", then the node will show "<Wait>".

If the wait nodes end up being a hassle, please send me steps to reproduce the issue. We can probably come up with a different workflow that you might prefer.