Savegame crashes after recent update (and hotfix)

Same for me. Game crashes in latest preview branch when loading save games from stable. 

@Bomato Mind posting a new bug with your log and save file? There are many reasons the game could crash, probably worth looking at yours individually.

Changed Status to Known Issue

@Ipsquiggle, thanks for letting me know. Posted it here: 

 

Edited November 23, 2018 by Bomato

@blash365 Is there any chance you have a save from before Abe got into the rocket?

Just now, Ipsquiggle said:

@blash365 Is there any chance you have a save from before Abe got into the rocket?

Yep. But it would be very old. Like 800 cycles.

@Ipsquiggle: My manonthemoon savegame is the latest savegame i have from before abe entered the cursed rocket.

@Ipsquiggle for osx,with same issue should i make another thread? or post log/save here itself.

Edited November 24, 2018 by ozymandias_3

I'm also having the same problem. In my case I reloaded an old save that didn't crash but end up with the same problem. Everytime a rocket comes back from a trip it will freeze the game. I'll have to force the quit of the game. Then I'll reopen the game and try to load any of the auto-saves, but all of them are corrupted, crashing on load. To play again I have to reload a save before any rocket launches. Attached are two auto-save files, cycle 806 rockets are not launched, loads without crashing, cycle 807 rockets are launched and game crashes on load.

sconet 2nd rocket Cycle 806.sav

sconet 2nd rocket Cycle 807.sav

Edited November 24, 2018 by kirani

@kirani as it so happens, i have a rocket returning as well. A save before the launch loaded fine.

 

So I loaded the save prior to launch, launch and return were normal (no crashes), went further into few more cycles. That save is not loading.

Edited November 25, 2018 by ozymandias_3

@kirani Your crash was slightly different and will be fixed in the next hotfix. For everyone else... still investigating. :\

Changed Status to Fixed

Thanks so much for all the info! This will be resolved in the next hotfix.