Dialogue Editor bug?

[nathanj]

Edit:

I changed the name to correctly label the editor.

I’m getting this strange behaviour where if I generate a new conversation in the Dialogue Editor, select a different conversation and then return to the newly created conversation the Start node has disappeared. I need to close and open Unity to be able to edit the newly created conversation.

Can anyone else check to see if this is happening on other systems?

I'm using Unity 2018.2.17f1 and DS 2.09

Thanks,
Nathan

[Tony Li]

Hi Nathan,

Are you changing anything on the new conversation's <START> node? (It's best to leave the <START> node alone.)

Are there any messages in the Console window?

Can you go to the Database section, expand Editor Settings, and click Debug? This will log a lot of info to the Console. If you can reproduce the problem, check the Console for any message that looks suspicious.

Is it possible that the canvas is scrolled away from the <START> node? What happens if you select Menu > Center on START?

[Japtor]

Hi Nathan and Tony,

I am using the Unity version 2018.2.12f1, the Dialogue System for Unity 2.0.9 an I am having the exact same issue.

if I generate a new conversation in the Dialogue Editor, select a different conversation and then return to the newly created conversation the Start node has disappeared

For me, in the new conversation the Select Menu -> Center on Start is in grey form (not interactable).

Spoiler

Also, I have done the Debug part as you mentioned, and here are the results:

Spoiler

(Create new conversation -> Select different one -> return)

Any idea?
Thanks!

[Tony Li]

Thanks! I'm looking into this. I'll try to have a patch ASAP.

[Japtor]

Thanks, Tony!

If you can, comment here when the patch is available!

[Tony Li]

The bug is now fixed in version 2.0.9-Patch20181214, which is available on the Pixel Crushers customer download site. If you need access, please PM me your Unity Asset Store invoice number.

Version 2.0.8 introduced caching in dialogue databases, which was the first step in implementing a major optimization of resetting, loading, and saving databases at runtime. The optimization is complete in this patch, and will also be in version 2.1.0. One studio with an extremely large database saw a 100x speed increase.

The bug occurred because in certain cases the editor didn't update the cache when adding new conversations. The patch makes sure that the cache is always up to date.

[nathanj]

Thanks for this. Was wondering if it was related to that.