Page 1 of 1

[2.0.60] Save file corrupt, unknown protoype ID 255, failing hardware.

Posted: Fri Jul 25, 2025 6:16 am
by MojitoHappiness
"Corrupt map: unknown quality prototype ID 255. File has likely been corrupted due to failing hardware."

I have ran diagnostics and there were no errors on RAM


I think that this is a similar situation to other posts I've seen, where a single byte was corrupt, and the world might be recoverable.

What did you do?
I was playing factorio and suddenly game just gave me an error that my map have been corrupted and from that moment i can't load it. I wasn't doing anything too unusual. My character was on Aquilo, but I was working on a Vulcanus making more iron plates, placing beacons with speed modules and foundries with productivity.

What happened?
I think some byte corresponding to the ID prototype was corrupted, and so the 3 auto saves got corrupted too but the save i made 3 hours before or so, works.

What did you expect to happen instead?
Nothing, was just playing with mods.

Does it always happen?
It happened to me first time in my multi thousand hour journey in this game

Log File
attached

Further information
This was on a Space Age world, with quality and elevated rails. There were mods installed and enabled.
This was on version 2.0.60. The world was corrupt a just now, and I rally want it to be saved by a recovery.
This was on Windows 11, with 32 GB ram DDR4, rtx3080 and Ryzen 7 5800X


Dropbox link to the corrupted save file:
https://www.dropbox.com/scl/fi/yh3c6jaz ... ygig1&dl=0

Re: [2.0.60] Save file corrupt, unknown protoype ID 255, failing hardware.

Posted: Sun Jul 27, 2025 11:08 am
by boskid
Suspicious... Corruption here is of exactly the same type as in 130049 - 5th item filter, corrupted exactly the same way as in the other topic with exactly the same values (Notes: FF FF FF 7F)

130029-Space Age Mojito-fixed.zip
(54.37 MiB) Downloaded 10 times

Re: [2.0.60] Save file corrupt, unknown protoype ID 255, failing hardware.

Posted: Mon Jul 28, 2025 3:01 am
by MojitoHappiness
If that is RAM even after doing 2 hour diagnostics that said no errors it must be RAM anyway i guess, I'll get new one to be sure then. And thank you for the fix so much! WIsh there was some way for me to do it myself so i don't bother You.