Hi!
So I have two subtitle panels, and mid-conversation I change them with SetPanel command. This works except for one bug.
When the dialogue comes up with a character who last spoke with the previeous panel then both panels show up. With previous panel having the old dialogue text.
So, for example:
NPC 1: Dialogue shown in Panel 1
NPC2: SetPanel to panel 2 sequence command
NPC2: Shows only panel 2
NPC1: Shows both panel 1 and panel 2. The panel 1 has old dialogue.
Visibility on both is set to "Only during Content". I do this for two reasons:
1) I only want to show either dialogue panel or responce panel not both.
2) I want dialogue panel to automatically get hidden if I have empty dialogue text node that I use for cinematics.
I tried adding empty text dialogue node to NPC1 before calling SetPanel command, but that didn't work.
Thanks
An issue with multiple subtitle panels
Re: An issue with multiple subtitle panels
Hi,
What version of the Dialogue System are you using? This might have been addressed in an update.
I'll also try to reproduce it tomorrow morning with the latest version (2.1.6). If I can reproduce it, I'll put out a patch to fix it.
What version of the Dialogue System are you using? This might have been addressed in an update.
I'll also try to reproduce it tomorrow morning with the latest version (2.1.6). If I can reproduce it, I'll put out a patch to fix it.
Re: An issue with multiple subtitle panels
I haven't been able to reproduce the issue you described. But I'm sure my conversation is set up at least slightly differently from yours. Can you email a copy of your scene and dialogue database to tony (at) pixelcrushers.com?
This is the test that I set up:
SetPanelTest_2019-05-25.unitypackage
(Exported from Unity 2018.1 and Dialogue System 2.1.6.)
This is the test that I set up:
SetPanelTest_2019-05-25.unitypackage
(Exported from Unity 2018.1 and Dialogue System 2.1.6.)
-
- Posts: 112
- Joined: Tue Jan 19, 2016 11:37 pm
Re: An issue with multiple subtitle panels
Thank you. I had DS 2.15, I'll update to 2.16 and report if the problem persists.