[StrangePan][2.0.34] Crash loading 2.0.33 save "Minimally-active segmented units count doesn't match."

GlassBricks · Post by **GlassBricks** » Fri Feb 07, 2025 1:25 am

After updating to 0.34, get a crash loading a 0.33 save.
Crash message indicates this might be because I was doing demolisher shenanigans in editor mode (deleted some naturally spawning ones, added then deleted more).

Log and save are attached.

Edit: attached the correct log file this time

GlassBricks · Post by **GlassBricks** » Fri Feb 07, 2025 2:04 am

update... the same error seems to occur when loading the save in 2.0.33, when adding a new mod.
This might point to it being in the migration logic somewhere?

Post by **StrangePan** » Fri Feb 07, 2025 1:46 pm

Hey, thank you for the report. Sorry about that, it seems your 2.0.33 save was corrupted. Here's your fixed save.

Thank you for the report. I'll work on fixing the bug so that other maps don't get corrupted as yours did. If you encounter this issue again, please update the main thread. I'll mark this one as a duplicate. 126642

Factorio Forums

[StrangePan][2.0.34] Crash loading 2.0.33 save "Minimally-active segmented units count doesn't match."

[StrangePan][2.0.34] Crash loading 2.0.33 save "Minimally-active segmented units count doesn't match."

Re: [2.0.34] and [2.0.33] Crash loading 2.0.33 save "Minimally-active segmented units count doesn't match."

Re: [StrangePan][2.0.34] Crash loading 2.0.33 save "Minimally-active segmented units count doesn't match."