First text of a conversation node doesn't get displayed.
Posted: Thu Oct 26, 2017 11:04 am
Hey,
I've got a problem with the Dialogue System.
I use Unity 5.4.0f3 and Dialogue System Version 1.6.8..
The problem is that sometimes the first text of a conversation node doesn't get displayed.
I use the modified Typwriter Effect that scrolls automaticly with the text.
I can't pinpoint it to a specific event, because it happens at one point and a few hours or a build later it works as intended.
What I can say is, that it always happens at the first node of a conversation with text in it.The next node works fine.
In the UnityUIDialogueUI class the ShowSubtilte methode is called and the Subtitle object contains the wanted text.
But in the UnityUITypewriterEffect class, when the methode GetCurrentText() is called, the current object is always empty.
No string file gets build up.
There are no empty spaces before the text in the node and if I put a new node as first node, the same thing happens to the nex node.
Maybe you've got an idea what the problem is. To me it feels like it might be a timing problem. But I can't figure out where to look.
Thanks in advance.
I've got a problem with the Dialogue System.
I use Unity 5.4.0f3 and Dialogue System Version 1.6.8..
The problem is that sometimes the first text of a conversation node doesn't get displayed.
I use the modified Typwriter Effect that scrolls automaticly with the text.
I can't pinpoint it to a specific event, because it happens at one point and a few hours or a build later it works as intended.
What I can say is, that it always happens at the first node of a conversation with text in it.The next node works fine.
In the UnityUIDialogueUI class the ShowSubtilte methode is called and the Subtitle object contains the wanted text.
But in the UnityUITypewriterEffect class, when the methode GetCurrentText() is called, the current object is always empty.
No string file gets build up.
There are no empty spaces before the text in the node and if I put a new node as first node, the same thing happens to the nex node.
Maybe you've got an idea what the problem is. To me it feels like it might be a timing problem. But I can't figure out where to look.
Thanks in advance.