Beta with new UI enabled crashed when attempting to auto-save during zone transition

[Jay Little]

So while playing with the new UI enabled that premiered in last nights beta, I got the message pictured in the screenshot which I actually have never seen before. Zipped up save directory attached. I reloaded the previous save (which is attached) and was able to replicate within a few screen transitions… though it happened in a different screen and took a few minutes of game play and exploration to replicate.

[Jay Little]

I can confirm that once I turned off the new staging UI, I was able to proceed without issue. Made it all the way back to Joppa.

System Specs: Pop! OS 20.04, Integrated Intel Graphics

[Corey Frang]

If you run into it again can you track down the Unity Player log and post it?

[Jay Little]

My Linux systems don’t seem to generate a unity player.log file. I tried finding one during my stream last Tuesday when it crashed and was unsuccessful. This happened on a separate computer, but still running Linux and while this computer did have a player.log file, it had last been updated on 4/28 so it wasn’t really relevant. Is there something I can do to get Qud to create that file?

[Jay Little]

Of course just I ran Qud from the terminal and it told me where the log is located…. I guess you guys just moved it:

~/.config/unity3d/Editor

I’ll attempt to replicate it again and post the log here.

[Jay Little]

Its from a point further along in the game, but it appears to be a serialization issue based on the stack trace at the end of the log.

[Brian Bucklew]

assuming fixed in 201.x