[2.0.30] Game save crashing on consistency check after 2.0.30 release (UpdatableEntity.cpp:120: this->chunk)

[phillycheeeeez]

Since the 2.0.30 update my game has been crashing on the "checking consistency" step when trying to load some of my game saves. This was not occurring prior to this update.

In my search I found that similar issues were occurring where it was suggested that this may be an issue of hardware failing. So far, I have ran diagnostics on my RAM and not found any issues but have not yet tested other components, although I don't expect to find any issues as this is a relatively new machine and I have not been experiencing any other issues.

Below is a link to the game save file that is erroring. For some reason it will not upload successfully as an attachment to this post so I've uploaded it to my Google drive. Hopefully this is acceptable.

https://drive.google.com/file/d/1shXV2N ... drive_link

I've also attached a working game save file from 3 weeks and logs from the most recent crash.

Any help is appreciated. I've got close to 1000 hours put into this save and I really don't want to have to start over form scratch if this isn't fixable.

[boskid]

Consistency check correctly detects a consistency issue because there is a medium-wriggler-pentapod-premature on gleba which reports as being at position {20.519, 511.316} (that is chunk[0,15]) however it is registered as active on chunk[15,-4]. I cannot simply move this entity to be on chunk[15,-4] because it is also a military target which is registered on chunk[0,15]. This unit also reports as being owned by a spawner that exists on chunk[15,-3].

I have no idea what happened here and i do not want to be doing any hex editor manipulations to try fix this. If you are desperate to loading this save file, you can go to hidden settings and turn "consistency-check" option to "never" to load this save file regardless of the inconsistency in it, try removing this unit (it is on gleba near position {20,511}) and then saving again. After this i can suggest turning "consistency-check" to always so if there is a failing hardware involved you will get notified of this a lot earlier than when game updates.

01-21-2025, 19-18-15.png (464.56 KiB) Viewed 526 times

[phillycheeeeez]

Thanks for the reply. This was very helpful. I've located the entity in question and tried shooting it and throwing grenades at it but my game crashes every time I try to destroy it. I was worried this might happen, but was hopeful enough to believe that brute force would be able to solve my issue. Alas, this insignificant pentapod is becoming the bane of my existence. Is there another way of removing it that you suggest I try?

Attached is the crash log of when I try to blow it to smithereens.

[boskid]

This is what i was afraid could happen, i also tried going to the position where this entity originally was supposed to be (going east on gleba to visit chunk[15,-4]) but as soon i got close to them the game also crashed because this unit became active (as part of being registered on one of those chunks to become active when enemies are around), it timed out and tried unregistering from the surface. I will take a look if this is easily fixable but right now even entity position saving is in my way causing problems so in order to fix this i will have to unfortunately resave the game in a fixed state (compared to hex editing which seems to be not available in this case).

[boskid]

It was exactly as i predicted from the consistency checks: at the current position this wriggler was throwing on consistency check for updatable entity, but when i moved it to where it was supposed to be it started throwing on consistency check for military target. Because of this i forced this entity to be at [gps=493,-112,gleba] and had to rebuild part of the military targets structures. With this i was able to resave this save file in a fixed state.

From this point forward i am kindly asking you to enable the consistency-check=always so if a similar issue would happen again you will get notified more quickly.

fixed save file resaved on 2.0.30:

126202-phil-fixed.zip

(82.86 MiB) Downloaded 35 times

[phillycheeeeez]

Thank you! I've loaded the file you attached and it appears to be working once again.

I've also gone ahead and configured the consistency check to always occur, per your recommendation.

The amount of gratitude I have for you and your entire team is immeasurable. Thank you so much for the swift response and resolution.