[2.0.21] Crash when loading save (TransportLine.cpp:889: this->items[i].distanceToNext >= 0 was not true)

[malison]

I believe I'm facing the same issue starting with [2.0.20]. My previous save and autosave from the previous version do not work.

What did you do?
Continue previous save

OR

Select Single Player > Load Game > select an _autosave file

What happened?
The game started to load, but crashed after "Checking consistency"

11-20-2024, 22-18-03.png (11.17 KiB) Viewed 406 times

11-20-2024, 22-18-39.png (15.73 KiB) Viewed 406 times

What did you expect to happen instead? It might be obvious to you, but do it anyway!
I expected my saved game to load normally.

Does it happen always, once, or sometimes?
This happens every time since 2.0.20

Save Game Download:
https://drive.google.com/file/d/1XUQlrY ... drive_link

Update:
I tested this in 2.0.21 Experimental and the issue persists.

11/22/2024 Update:
I haven't been able to play since 2.0.20 so I decided to try older versions.

Crash
Saved Game Loads and is playable

- 2.0.22
- 2.0.21
- 2.0.20
- 2.0.19
- 2.0.18
- 2.0.17
- 2.0.16
- 2.0.15

[Rseding91]

Thanks for the report. This specific error indicates that some fundamental corruption has happened with the save file which should never have been possible. Do you know of any way to take a known good save file and get it into this corrupt state? (without changing game versions)

In the past, this issue was a good indicator that the computer's hardware is failing/has failed.

[malison]

Unfortunately, I don't know how it got into this state.

I was playing on an earlier version of the game. I saved the game normally. The next day, after Steam auto-updated to 2.0.20, I could no longer open the saved game.

I can open the save in 2.0.15 and everything seems to work fine.

I played a bit and saved it again to see if that would fix it, but I'm still unable to play on anything newer than 2.0.15.

Let me know if there's any other way I can help.

[malison]

Same crash in [2.0.22]

[Rseding91]

Same crash in [2.0.22]

The save file is corrupt in a way that should never be possible. New versions won't fix that corruption since as far as we can tell code wise it should never be possible to have happened in the first place.

If we could identify how it happened then we could get it fixed. But so far, the only common case is the player eventually finding their hardware is failing.

[malison]

That makes sense, but I can still open the save file and play normally on 2.0.15. Why would that work but newer versions do not work?

[boskid]

When save file is loaded in newer game version or with a different mod composition (when installing or removing mods), a consistency check is running that is able to detect this issue. When you remain on the same game version as when the save became corrupted, consistency check is not running and the save file appears as being fine while in fact it is still corrupted. You may be able to load this save file in 2.0.15 but if you hold Control key while clicking "Load" button in load gui, it will also crash because the save file will be loaded in a mode where it also checks consistency.

[malison]

Thanks for the explanation!

There's definitely something hardware-related going on. My entire system crashed—it just rebooted, with no blue screen or OS issues.


I guess I'm stuck on 2.0.15 for now.

[mminkov]

Sorry, is there a way to say "I know what I'm doing" and load the file *without* consistency checks?

My last good save is 2 days ago, even though the game was working perfectly fine last I checked.
At the very least I'd like to copy a blueprint of my base and paste it on the last good save. I'll install an older version for that, but still...

Uploading a log, in case it gives more info.