[2.0.17] Failure to open most recent autosave after crash.

[Shantogen]

11-12-2024, 14-37-14.png (42.2 KiB) Viewed 318 times

11-12-2024, 14-37-48.png (241.28 KiB) Viewed 318 times

Happened to me a few times now and still trying to figure out what exactly causes it but here is what I got:

This happens usually with the most recent autosave and only after a game crash. This does not happen after every game crash and I have not run into this problem on the non-experimental version after a crash.

Something to note. This does seem to happen EVERY time I crash AND there is a new update.

I usually dont lose much as I set my autosaves for very short but its happened probably 3 to 4 times since I changed to the experimental. It usually coincides when the game crashes and there is an update. This does not seem to be the case with the non-experimental release or atleast I have not come across this specific scenario outside of the experimental release.

Let me know if you need any more details.

11-12-2024, 14-43-40.png (50.79 KiB) Viewed 318 times

[Rseding91]

Thanks for the report however I'm not seeing anything here for us to fix. The game is not supposed to be crashing - if it is - and you have steps to reproduce that crash - let us know those steps. If you don't have steps, and it's random - plus you're getting bad ZIP files. That says "failing hardware" to me.

[Shantogen]

Thanks for the report however I'm not seeing anything here for us to fix. The game is not supposed to be crashing - if it is - and you have steps to reproduce that crash - let us know those steps. If you don't have steps, and it's random - plus you're getting bad ZIP files. That says "failing hardware" to me.

Did some stress testing and this seems to only happen under a very specific set of circumstance. So specific that in retrospect I would prolly not have submitted this report. but for full transparency:

This happens only specifically under the following circumstances for me:

1) Game does not close properly. Whether it be from an in game crash or hardware crash seems not to matter but I mainly tested this with hardware interrupts to try and get to the bottom of what was going on.
2) It only affects the most recent autosave prior to crash. any other saves and autosaves are not affected.
3) I have only been able to replicate the bug when a new version is patched between crash and relaunching the game.

More detail description:

I am still not sure what is causing this but from my previous experiences and testing I can at least rule out anything from a normal operation. it seems just to be under the specific circumstances when it crashes and there is an update/patch waiting to be added. I should also clarify I use steam.

My best guess is it probably would have to do something with a version mismatch though I am unsure how it would only affect the most recent autosave instead of any prior save. the fact that it only happens under the specific circumstance of having it crash while an update is pending is also a highly specific problem.

I can say out of the 3 times I have crashed 2 were on my hardware. one was a crash I don't have any record of what happened as it was during a time I as not at the computer and just had Factorio running in the background. this crash was specific to Factorio but I again I was not at the computer at the time so I cant say what happened or why. The other 2 crashes were computer freezes which was easy to identify on my end as well, coming back to a non-responding computer is a high indication that's on me. I chose not to report this those times as I assumed it was a "me problem" but when I returned after 3 hours to a fully running computer and seeing Factorio had crashed and when I came back in a patch had been applied and the file unable to open encouraged me to make a post.

Suggested action:
Probably safe to disregard this unless it shows up from someone else. This very well be an only me thing and perhaps it was Factorio that crashed but something on my pc that closed it. Who knows. Maybe my cat jumped on the keyboard and accidentally atl+f4 it for all I know. If you would Like I can delete the post. Let me know and sorry for the bother.