Preventing glitched Persisents

[styckx]

As long as I've been playing this today had my first corrupt save.. I noticed it when I was driving a rover I had on the Mun.. Almost predictable hitching every 10-20 seconds.. Then when starting the game it was slow to bring up the resume screen, then slow to bring up the saved game list, slow to load the VAB.. Everything was slow. I then also noticed a lander I had just landed on the Mun was mysteriously gone. It clicked with me then my save was most likely corrupt. So I went one by one in my tracking station deleting each flight (I had a backup save) until I notice the glitchy slow game play go away. The buggy game play was narrowed down to the rover which was one of the first vehicles of this save.. Copied over my backup, deleted that one flight and everything was kosher again.

I'm sure others have experienced this.. How do you prevent your save getting corrupt like that? In over two years this is the first time I remember this happening but now my Tech OCD anxiety is fearful this might happen again.

Edited July 24, 2014 by styckx

[rabidninjawombat]

I play with alot of mods, so i general backup my save folder/GameData every couple of days at least (Just basically copy paste them into another folder for safe keeping) If something happens to my save, ill revert back to the most recent save/gamedata

[Cydonian Monk]

Prevent corrupted saves? Not sure that's possible. I've just learned to live with it, and to keep my saves backed up by DropBox. Whenever I notice it going batty I either fall back to a previous version or manually copy over the missing craft (using vim) if I'm too far along from when it was lost.

[Spyritdragon]

Make a backup every few days, or just at the start of every day if you feel like it. That way, if your save file ever corrupts, you can reload it :-).

Plus, it also works when you forget to quicksave and then, say, do your orbital rendezvous closest-approach a little toooo perfectly.

[katateochi]

I have been writing a tool for this exact reason. It's called Jebretary (secretarial staff for your space program) and it maintains automatic version control of craft, subassemblies and save files. If either you or KSP muck up a craft or save file you can just click on a previous version and go back to how it was.

With save files (persistent and quicksave) and subasemblies a new version is marked each time they change. With craft it waits to mark a new version until you launch the craft, this way you get a version for each variation you deemed worthy enough to do a test launch. You can also force it to mark a new version at any point.

You can also load a persistent files as a quicksave, so if you forgot to quicksave and then some horrible bug happens, don't panic, you can just load up the last autosave as a quicksave.

Jebretary doesn't just take copies of files (which is kinda inefficient, especially for saves with lots of in-flight craft), it uses the GIT version control system to track the changes. This means it tracks just the lines of the files that have changed which is much more efficient.

It also has other features like enabling you to archive craft by deleted them (you can restore them later if you need), it tells you what parts (and therefore which mods) a craft uses and if any of its parts are missing, it can move/copy craft between different campaigns or installs of KSP and you can also write notes about each version of a craft or save file (useful when looking back to find the right version to reload).

get Jebretary here

Edited July 24, 2014 by katateochi
speelong mistaks

[Russoft]

learn how to fix your save files, or make back ups. Fixing them is a pain and I don't know if it's always possible. Much easier to have a back up from the near past to revert to.