why are saves always breaking after you played them for some weeks

[micr0wave]

sry in advance for raging a tiny bit, BUT now it's the 4th-5th time saves getting unplayable after some weeks of playing them, be it kraken attacks, the 'can't-switch-back-to-anything', Unknown Mystery components and a good portion of minor things.

So i'm slowly starting to think anything a bit more complex than shoot a rocket somewhere and bring it back asap before crew/ship/whatever bugs out is the only thing to do.

All those gamebreakers happened on different mod combinations, but i noticed that it must be some stock problem, since i see quite some people with the exact same symptoms on forums/streams (and soon in prison cells for going berserk after the 10th save becomes corrupt ).

So, is there any hope left to get some bigger things going for longer than some days or should i take a vacation and hope the best for 1.0 ?

[Richy teh space man]

Are you firing Kerbals? That's a known issue at the minute

[Deutherius]

Personally, I have never had a save file corrupt itself, most gamebreaking bugs (stuck in LANDED state, exploding wings, UI not responding...) were easily resolved by restarting the game and frequent quicksaving so I have a savepoint to go back to. I don't use any seriously game altering or part adding mods, though.

I very much doubt it's all stock game problems (especially the "Unknown Mystery components"). A quick search shows you use a lot of mods... At that point it might be like mixing many different medications, not even the doctors are completely sure what happens.

Your best bet is assembling a thorough investigation of the problem/s at support forums. Probably not what you wanted to hear, but I don't think you're gonna get any/all of your problems solved here.

[micr0wave]

it's some bugs which happen after you played them for longer time for me. It's not tied to my current combination of mods since i suffer that problem since 0.2x even with almost no mods, it will happen after some time. Add to that that i am not alone with those bugs, it's more likely that the error isn't related to 100% on my end. And to point out that 'reload often enough and it might work at some point' pretty much hints that some code isn't working with just false/true but has also the boolean value of 'maybe'

edit: @Ricky no, didn't fire anyone and i have claw's stockbugfix thingie

Edited March 19, 2015 by micr0wave

[WuphonsReach]

Backups are a must with KSP. Use the S.A.V.E. plugin and/or Kerbal Alarm Clock along with your operating system's snapshot backup feature (System Restore Points on Win7 or later) or some other external backup program.

[eddiew]

Every day at the start of a KSP session, make a save called "2015-03-19 daily" etc.

Takes 5 seconds once you're in the habit

[micr0wave]

i have security backups of my saves, that's no problem, but when after trying a couple rewinds to different saves (i went back some hours, more hours, days, weeks), you play the same thing through again and again and again just to find out, no matter how far you go back, it's broken, what's the point of even trying to use that save anymore ?

I just had to vent a bit, but the point still stands, jammed docking ports, unresponsive kerbals, clones, krakens, you name it, i'll get it, given enough time.

[eddiew]

Jammed docking ports often turns out to be an old version of Kerbal Joint Reinforcement... if you're using it, make sure you're getting the latest build off GitHub, not the general download link