[V.1.197.170][BUG][LEGACY SAVE]Savegames Pre 10-2016 Corrupted

New patch corrupted a third of my old saves

Booted up the game today, got an Eula i agreed to, game started, went to the loading screen message says:

One of the world/save files is corrupted and can't be loaded.

See log for details.

that is 32 of my 97 saves are in red that the game assumes corrupted.

That is every save pre 06/11.2016

after that most work with exeption of:

one dated 12/12.2016

two dated 10/6.2017

Maybe they already were corrupted and with the new patch does a "check for corrupted saves" now, but i am pretty sure that i didnt have 32 corrupted saves last i booted the game.

in the earlier days, we could use SEToolbox to repair corrupted worlds, is there a way for me to recover theese worlds now? (apart from spending hours on hours downloading an older version of the game client, booting up SEToolbox, repairing the files and then reload the saves in the updated client?)

Previously one could use tools like SEToolbox to work around corrupted saves by deleting corrupt content, but today it seems i need to spend a day or more to download and install old build, Save all the files, update the game again to the lates build and save them once more.

There should be an official "fix legacy savegame" that has some powertool options for fixing this issue. Examples like

"Extract blueprint from grid" (with a list of grids with attached subgrids)

"Remake in empty world" (make an empty world with only the built grids)

"Update to latest build" (updates and saves the game to the latest build)

As noted by Steamuser: fabricator77

As per usual with these corrupted saves, there is nothing wrong with the stations, ships, asteroids or planets. The save file containing all this information (SANDBOX_0_0_0_.sbs) is perfectly fine.

What is wrong is missing data in SANDBOX.sbs , which is just the world settings, list of mods, player data etc. It is NOT corrupted, damaged, or broken. This config file is simply an old version, which lacks some information.

Something in the <SessionComponents> section if I recall.

Tips to fix this, without having to resort to multi GB downloads of an old version of the game, then downloading the current version all over again.

Steps (try at your own risk, make copies of saves before messing with)

1. Install Notepad++

2. Rename SANDBOX.sbs to say SANDBOX.sbs.old

3. Beg, borrow, or steal SANDBOX.sbs from a known working save.

4. Open both files in Notepad++

5. Copy the SessionName from the old file into the new one. eg <SessionName>Asteroid Base - TPD 4622</SessionName>

6. Copy the list of mods over as well.

7. (maybe) copy over the list of players/NPCs as well, if you care.

Link to steam forum post:

https://steamcommunity.com/app/244850/discussions/0/?fp=2

Link to Corrupted saves and .log file:

https://www.dropbox.com/sh/lbv0v9tmeorfml2/AADSgGsJe8YATIbKa1Am14sPa?dl=0" rel="nofollow" target="_blank">https://www.dropbox.com/sh/lbv0v9tmeorfml2/AADSgGsJe8YATIbKa1Am14sPa?dl=0">https://www.dropbox.com/sh/lbv0v9tmeorfml2/AADSgGsJe8YATIbKa1Am14sPa?dl=0

This is important as there are thousands of gigabytes of legacy SE content with players, and loosing your old stuff in a game like this is not good. it would be like loosing a creative lego build you spent days, weeks months on that you put up on a shelf for safekeeping but due to lego making new bricks, the build vanishes into thin air never to be seen again.