[2.0.41] biter not registered on chunk?

[Socax1]

i had previously posted an issue with this savefile, all i received was a post title change and nothing else. viewtopic.php?t=127451 . With [2.0.41] released i had hoped the issue would have been corrected but perhaps i was too selfish in my optimism. launching the game in [2.0.32] allows me to play. however, the game seems to crash whenever the game tries to autosave, which i have set to every 5 minutes. Sometimes it autosaves without issue but most of the time the game crashes. I am running no mods apart from base + space age. I was able to get maybe 30-45 minutes of in game time in before i could not take it anymore. launching this save file (in [2.0.41]) or any other save on this world produces the same result as in [2.0.36]. i have attached "autosave 1" which is my latest autosave in version [2.0.32] and "y76" which is my latest manual save in the same world, named after my 76th session. if there is anything else i am missing or yall need more files or information please know that i am frantically scouring this forum every few hours so dont be afraid to ask. i really dont want to start again. ill give yall my SSN if thats what it takes. i understand this may be a duplicate post but i ask the moderators to keep it up, bause if i have learned anything in my career its that more tickets = more attention. Our lord in heaven, kovarex be thy name, save me now. amen.

[eugenekay]

Hello,

The Error message mentioned in your previous post & Title here is related to a piece of Verification code for loading Biters, which is reporting that there is unexpected / corrupt data in the save file. This is a “single byte” type of error, which means that it May be a Hardware Problem with your computer that “flipped” this bit, such as a failing Memory cell, or a Cosmic Ray Collision. Factorio cannot fix this automatically because it does not know which way that the Byte flipped. The best way to prevent these is to use a system with ECC RAM, such as a Workstation style machine; or turn up the number of Autosaves (and check them!).

You can attempt to fix this Save file using some Console Commands to remove enemy units and then re-Save with a new Filename. There are no guarantees against other, undetected corruption.

Good Luck!

[Socax1]

Thanks I’m gonna try this