Page 1 of 1
[2.0.14] Invalid bool loaded from input file. File could be corrupted.
Posted: Sat Nov 02, 2024 6:27 am
by jy314
1. Not long ago today, I tried to open yesterday's archive and continue designing an assembler system using the operator.
2. but it didn't work, the archive failed to open and displayed an error report as in the title.
3. I tried a number of things, including changing the archive configuration and rolling back the game to beta 2.0.13 (yesterday's version, when everything worked fine), none of which worked.
4. I searched the web and forums for related issues and found the same thing, but I did not find a viable solution.
Is the problem fixable? If yes, what should I do?
Re: [2.0.14] Invalid bool loaded from input file. File could be corrupted.
Posted: Tue Nov 05, 2024 3:30 pm
by Tesse11ation
I just had the same issue on my 2.0 dev world (singleplayer with cheats for designing blueprints). There wasn't even an update between the last time I loaded it and now either.
I attached my save file in case this issue gets addressed and the devs would like another example of this to look at. Best of luck!
Update: All 3 of my autosaves from that world are also borked. And I was able to reproduce the issue on my Steam Deck since I have Steam Cloud enabled. Apparently, this is the only world that is throwing this error too since I haven't had the issue on any other save I've loaded up.
Re: [2.0.14] Invalid bool loaded from input file. File could be corrupted.
Posted: Thu Nov 07, 2024 8:34 am
by jy314
Tesse11ation wrote: Tue Nov 05, 2024 3:30 pm
I just had the same issue on my 2.0 dev world (singleplayer with cheats for designing blueprints). There wasn't even an update between the last time I loaded it and now either.
I attached my save file in case this issue gets addressed and the devs would like another example of this to look at. Best of luck!
Update: All 3 of my autosaves from that world are also borked. And I was able to reproduce the issue on my Steam Deck since I have Steam Cloud enabled. Apparently, this is the only world that is throwing this error too since I haven't had the issue on any other save I've loaded up.
My autosaves are also broken, but an old branch a week ago works, which makes me confused.
I've rebulid my blueprints in a new cheat world. But since I don't no why it happened, I have to save my blueprints and new branch flies every time I quit.That's the only way to prevents me from another heartbroken.
Seems there were posts with the same problem before the 2.0 dev updates, but no solutions given.