[2.0.21] Crash loading save after update (ElectricEnergySource.cpp:613: Invalid owner type)

[Iron Nerd]

When I attempt to load my last save, the game crashes during "running Entity Setup". The saves are from 2.0.20. An autosave when I landed on Gleba can be loaded that's also 2.0.20, but my recent auto saves all crash and the Gleba one is from 30 hours ago. No mods installed. I've updated graphics drivers, and even attempted to load on another machine and it still crashes. If I revert back to 2.0.20 they will load. Thanks!

[Rseding91]

Looking into your save file, there's an energy source from a solar panel (at least that's what it says) which is not owned by any actual solar panel entity. This should never happen - especially since every time the game updates it will validate that it has not happened (that's the crash you're seeing).

That means that while playing 2.0.20 some how it did happen. Is there any chance you know of a way to take a known working save file and get it into this state without updating the game version?

[Iron Nerd]

I've attached the last save that will work on 2.0.21. I wasn't able to replicate the problem. I didn't work too much on solar between the saves. It was mostly upgrading a solar patch beside my Nauvis base with quality panels. I did that with a combination of an upgrade planner and also manually replacing some panels. I did a little bit of solar on Gleba but that's about it.

[Iron Nerd]

I started playing around in the problem save looking for the "offending" solar panel. The game would crash after I removed a bunch of solar panels, but it wasn't a specific one that seemed to cause the crash. I eventually narrowed it down to a chunk of 1920 solar panels on Nauvis where it would crash if I removed any one in that chunk. I could build panels in the gaps and remove any as long as it didn't drop below 1920. I've attached the crash report and the save where it will crash with one more removal. The other planets and space platforms don't seem to affect it.

This still doesn't explain how the initial problem occurred, but I found it interesting.