Changes not saved to database asset

[Paddy K]

I love this tool, I really do. But I'm getting to the stage where I almost hate opening it. My work keeps getting lost ALL THE TIME. I save and save and save but all too often I come back to a conversation to find it's reverted to an earlier state and all my work is gone.

Just now I made changes to the dialogue tree and noticed the database asset file was not added to the list of changed files in github desktop. It appears that changes I made were visible in the editor, but were NOT being saved to the asset, despite me pressing CTRL-S constantly. When I opened the database asset file and MANUALLY added a change, then it showed up in github desktop, but only the manual change I've added, not all the others I've added through the dialogue editor.

And then if I open another conversation and return to the one I've been working on, my changes are not there, since they were not added to the database asset. All my work is then gone. For some reason, CTRL-S is not always saving the changes to the database asset. Often, but not always.

This is an EXCRUTIATING way to work, not being sure if changes will stick or not. It is in fact is a reason why I would not currently recommend Dialogue System to others. Saving is such a basic function. Please PLEASE fix this so I can continue using the tool.

I have Version 2.2.47 and am running Unity 2022.3.40f1

[Tony Li]

Hi,

Can you please update to 2.2.50.1? I'm really sorry for this. 2.2.50.1 should prevent the issue, but I'll also have a fix for the underlying issue ASAP.

Do you recall the circumstances under which this happens? This may be due to a known bug in Unity, which I may be able to help you with. I believe I implemented a workaround after 2.2.47.

[Paddy K]

Thanks for the super fast reply! We'll try that update. Fingers crossed...

[Tony Li]

If it doesn't address the issue, let me know if you were editing code at the same time. This is an obscure issue that seems to affect a very small number of projects. Once we had a workaround fix, I slowed the development of the replacement editor that fully works around the Unity issue. But if it's still occurring in 2.2.50.1, I'll bump that up to the very top of priority again and get the replacement out ASAP.

[Paddy K]

It works! Thanks for helping me so fast. Now it's fun to work in the Dialogue System again. Happy days!

[Tony Li]

Great! I'll continue to prioritize the new editor window, but I think the fix you're using should work around the Unity issue.