First text of a conversation node doesn't get displayed.

[Tabble]

Another day, another try

The script execution order didn't change anything. But I found the problem. I'm not enterly sure why. Maybe you've got an insight.
It happens in the UnityUITypewriterEffect calss.

Code: Select all

public IEnumerator Play()
{
     if ((control != null) && (charactersPerSecond > 0))
     {
      // Setup:
     InitAutoScroll();
     //yield return waitOneFrameBeforeStarting ? null : new WaitForEndOfFrame();
     if (audioSource != null) audioSource.clip = audioClip;
      ...
     }
    Stop();
}

I commented the line yield return waitOneFrameBeforeStarting ? null : new WaitForEndOfFrame(); because when the running system came to this point it just broke and moved to the code where it calls Stop() at the end of the methode.
It only happens if you switch a scene and the first conversation node with text gets displayed.

I hope that I have written it understandably. I'm still not sure why it breaks, but I'll investigate more.

[Tony Li]

Thanks for the info! I'll reproduce that here and try to provide a fix soon.

[Tony Li]

Just posting an update that a fix will be in 1.7.7, which is being released this week.

[Tabble]

Thank you

Can you tell me the reason why it happened? I haven't had the time to look into it yet.

[Tony Li]

Sure, here's the reason: The typewriter effect is on the subtitle line GameObject. This GameObject is normally disabled. The Dialogue System enables it when showing a subtitle. The typewriter effect starts typing when the GameObject is enabled. When it starts typing, it records the current contents of the UI Text, clears it, and starts typing it character by character.

There can be a race condition where the UI visually refreshes the UI Text component just before the typewriter effect receives the OnEnable method and starts typing. This makes the full contents visible for one frame.

To resolve this race condition, in version 1.7.7 the dialogue UI now explicitly tells the typewriter to start typing immediately after setting the UI Text contents, instead of waiting for OnEnable.