Pixel Crushers Forum

Hi!

I wish you all a nice sunday!
I have some performance issues in editor. When a conversation node is selected and it's content is shown in the inspector, the whole editor lags. As long as the node (or the database asset) is selected in inspector everything* slows down dramatically. Even when I start the game in Playmode, it lags, and I always have to make sure that I have no node selected when playing. Not a groundbreaking issue, but after some months it starts getting very annoying haha.

The database has currently 600 conversations. I guess that's the reason. In the end I will have around 1.5k so I'm a bit worried it will get worse. Is there something I can do? Or is splitting the databases the only option?

I'm using Version 2.2.8 in my main project. I created a new project with Dialogue System 2.2.16 and imported the database. It still runs very slow but a bit better.

I'm on Windows 10, Unity 2019.4.16f1. My PC should be able to handle it. Auto Backup freq is set to 360.

Thank you very much!

Edit: * by everything I mean all editor windows. moving nodes, scrolling through lists etc. as well as playing the game in Play Mode.

Hi,

Unity is not great at serializing large assets. Fortunately it's entirely an editor issue; it won't affect build performance. You may need to split your database. However, I am working on some additional performance improvements. Note: If you use OnExecute() events, close the OnExecute() Events foldout. When this foldout is open, the inspector must do extra work.

I see, thanks for the fast reply as always. I'll keep on working this way for the time being. If it gets even worse, I'll have to split the database up then. Thank you!

I have the same issue. Our Dialogue Database contains about 300 conversations, 250 items and 150 variables, and that's the third of the final contents. It worries me because it become harder and harder to work with Conversation Editor.
I figured out that it's solely problem with Unity, it lags when big asset is selected and displayed in inspector.
Our version of Unity is 2020.2.3, but I tested in 2021.2.3 and with empty project, but with no luck I also tried to clear out inspector drawer of Dialogue Database or profile with Inspector in debug mode just to check if performance improves.

You mentioned some work in performance. I'm currently using the latest v2.2.22. Do you have any improvements on this side?

Hi,

I recommend using multiple databases in that case.