Page 1 of 1

Performance Issues with StartConversation after upgrade

Posted: Mon Jun 07, 2021 10:04 pm
by Reznik
Hi, I recently upgraded DialogueSystem to latest and now it seems when I hit the line in my script for:
DialogueManager.StartConversation(title, DialogueManager.CurrentActor, DialogueManager.CurrentConversant, convoID);
which I have after stopping another conversation and changing the ui used, the scene and editor freeze up for about a minute before it continues on as it should. The only thing that's changed since this started happening was I updated to latest today.

I tried other suggestions in older threads around performance issues, but I can't seem to find something that fixes the issue.

Thanks!

Re: Performance Issues with StartConversation after upgrade

Posted: Tue Jun 08, 2021 8:06 am
by Tony Li
Hi,

Are there any errors or warnings in the Console window?

What is the Dialogue Manager's Other Settings > Warm Up Conversation Controller dropdown set to?

Re: Performance Issues with StartConversation after upgrade

Posted: Tue Jun 08, 2021 8:58 am
by Reznik
No warnings or errors and that setting on the manager is 'On'. Thanks!

Don't know if it is relevant but wanted to mention the conversation I'm using StartConversation on is the same conversation as the one I stop, just a later node.

Re: Performance Issues with StartConversation after upgrade

Posted: Tue Jun 08, 2021 10:42 am
by Tony Li
Hi,

When you say 'a minute' do you mean ~60 seconds?

Can you send a reproduction project to tony (at) pixelcrushers.com?

Re: Performance Issues with StartConversation after upgrade

Posted: Tue Jun 08, 2021 10:51 am
by Reznik
I will send a repro project. Thanks, I'm completely stumped on this one. And yes 40-60 seconds is the length of time it freezes for.

Re: Performance Issues with StartConversation after upgrade

Posted: Tue Jun 08, 2021 10:59 am
by Tony Li
Thanks. I'll keep an eye out for the repro project.

Also, if possible, please try backing up your project and updating to version 2.2.17 if you're on 2.2.16. (Version 2.2.17 just came out yesterday.) This way we won't be chasing down any issues that might already be fixed in 2.2.17.