Hello, I just updated to 2.1.4 (and after, 2.1.5) from 2.1.3 and suddenly, none of my conversations are working. In fact, what happens is that I see the dialogue box opening but it closes super fast. It looks like but looking at the Info traces that the whole conversation was played. I even compared Info traces between 2.1.3 and 2.1.4 and the only difference is that with 2.1.3, I see a warning saying that "Rewired: The action Cancel does not exist." I don't have that warning upon upgrading to 2.1.4, but it does work anymore.
Any idea on changes between 2.1.3 and 2.1.4 that could have caused this? Any place where I could look to resolve that issue.
Upgrading from 2.1.3 to 2.1.4 break conversation
-
- Posts: 106
- Joined: Wed Aug 23, 2017 4:10 pm
- Location: Canada
Upgrading from 2.1.3 to 2.1.4 break conversation
Unity 2022.3.17f1
Dialogue System 2.2.44.1
OpenAI Addon 1.0.12
Dialogue System 2.2.44.1
OpenAI Addon 1.0.12
Re: Upgrading from 2.1.3 to 2.1.4 break conversation
Hi Maxime,
I can't think of any changes that would cause this issue.
Does the Dialogue System's DemoScene1 work correctly?
If you temporarily set the Dialogue Manager's Debug Level to Info and play the conversation, does it run through the whole conversation immediately?
If you customized the Dialogue Manager prefab, did your customizations get overwritten?
As a test, what if you remove the RewiredInputManager and any Dialogue System - Rewired integration components such as InputDeviceManagerRewired and/or DialogueSystemRewired? It will use regular Unity Input in this case. This will tell us if the problem is related to Rewired (or the Dialogue System's Rewired integration) or something in the core Dialogue System stuff.
I can't think of any changes that would cause this issue.
Does the Dialogue System's DemoScene1 work correctly?
If you temporarily set the Dialogue Manager's Debug Level to Info and play the conversation, does it run through the whole conversation immediately?
If you customized the Dialogue Manager prefab, did your customizations get overwritten?
As a test, what if you remove the RewiredInputManager and any Dialogue System - Rewired integration components such as InputDeviceManagerRewired and/or DialogueSystemRewired? It will use regular Unity Input in this case. This will tell us if the problem is related to Rewired (or the Dialogue System's Rewired integration) or something in the core Dialogue System stuff.
Re: Upgrading from 2.1.3 to 2.1.4 break conversation
I also face the same issue after upgrading to 2.1.5
The NPC Node will play and end immediately ignoring the Delay() sequence despite subtitle or cut-scene setting too. For my case it happen at the last node before conversation end.
Dialogue System's DemoScene1 and 2 seem to work correctly
I did customized the Dialogue Manager prefab then it get overwritten with the update.
The NPC Node will play and end immediately ignoring the Delay() sequence despite subtitle or cut-scene setting too. For my case it happen at the last node before conversation end.
Dialogue System's DemoScene1 and 2 seem to work correctly
I did customized the Dialogue Manager prefab then it get overwritten with the update.
Re: Upgrading from 2.1.3 to 2.1.4 break conversation
Would either of you please send me a unitypackage containing your Dialogue Manager prefab, dialogue database, and scene? Or set the Debug Level to Info, play through the issue, and then email the Editor.log file to tony (at) pixelcrushers.com? Thanks!
-
- Posts: 106
- Joined: Wed Aug 23, 2017 4:10 pm
- Location: Canada
Re: Upgrading from 2.1.3 to 2.1.4 break conversation
Hello, it is in fact just like 8uddie said. I am using directly the Dialogue Manager prefab in my scene and I did save directly within the prefab some of my changes (Cancel Subtitle Input -> None, Show PC Subtitles -> Checked, Continue Button -> Optional). I even added a Rewired Input Manager script to the prefab and saved it like that. Upon updating to 2.1.4, my saved values within the prefab got replaced by the values you changed in the prefab for version 2.1.4.
I think I will create a Prefab Variant of Dialogue Manager prefab so that my modified values are not overwritten by your changes. It is really good to know as I was using directly your prefab.
I think I will create a Prefab Variant of Dialogue Manager prefab so that my modified values are not overwritten by your changes. It is really good to know as I was using directly your prefab.
Unity 2022.3.17f1
Dialogue System 2.2.44.1
OpenAI Addon 1.0.12
Dialogue System 2.2.44.1
OpenAI Addon 1.0.12
Re: Upgrading from 2.1.3 to 2.1.4 break conversation
Please let me know if everything is working correctly after making a copy of the prefab and adding your customizations again.
If you have a backup of your Dialogue Manager prefab, you can just restore it. Then make a copy and use the copy to be safe. I rarely change the Dialogue Manager prefab, but I did change it in a version control commit on January 27 to change a checkbox value.
If you have a backup of your Dialogue Manager prefab, you can just restore it. Then make a copy and use the copy to be safe. I rarely change the Dialogue Manager prefab, but I did change it in a version control commit on January 27 to change a checkbox value.
Re: Upgrading from 2.1.3 to 2.1.4 break conversation
Hmm.. I did re import the dialogue database and start clean seem be working fine
until i was starting to inputting the Dialogue UI and it occurred again
Then I can pinpoint that the problem seem to lay in the 'continue button'. disabling them seem to make it work.
I did make another canvas for them to achieve the 'click anywhere to proceed'
so somehow it force the last node of conversation proceed despite the sequence setting.
until i was starting to inputting the Dialogue UI and it occurred again
Then I can pinpoint that the problem seem to lay in the 'continue button'. disabling them seem to make it work.
I did make another canvas for them to achieve the 'click anywhere to proceed'
so somehow it force the last node of conversation proceed despite the sequence setting.
Re: Upgrading from 2.1.3 to 2.1.4 break conversation
Hi @8uddie - I'm having trouble understanding. If you're still seeing a problem, could you please post some screenshots that illustrate the problem?