1.10: A laggy buggy mess that may have corrupted a save file today...

[catloaf]

So 1.10 already had a few issues, big and small but this was surprising! So today after recovering a mission I saved only to find an error. Apparently this default name quicksave shared the and name with another one. The save file in question was displaying an error massage. I deleted the quicksave in question and tried to save, only to find the same error and a new bad file (I know this sounds like a console thing but it was on PC!) So then I tried to load persistent and nothing happened. However what's funny is that I could still interact with the game. I checked my output log and sure enough there was an error every time I tried to load a save or leave the load save box (can't tell you what the errors were, because I did not write down my log, but it appears to be failing to access files.) So then I proceeded to try and launch a vessel. But then the game got stuck in the vab (hard to describe) so I was forced to alt + f4 it. My only hope now is that persistent loads because it seems fine. This whole thing happened in the ksc screen so it was probably stupidity on my part, and I'm also not asking for help, just trying to get my voice heard, but I have been saving in the ksc screen after a play session every time since 2015 when I started playing and this has NEVER happened before. I love 1.10, but the collaborative station I'm part of is probably the only thing preventing me from reverting to the better performing and more stable 1.8.

Just so you know, in 1.10 the game has crashed 20 times randomly, meanwhile 1.8 installs with many mods only crash when you would expect them to (loading a 4000 part vessel that blows up in the pad.)

Long story short: I have never had to fear for my progresses safety more than in 1.10

I'm super lucky that I did not care about this save, never saving in ksc screen again.

Edit: wow, ranting about an issue really does get it off my chest.

Edited July 8, 2020 by catloaf
If this happens again I will post a log.

[Ruedii]

Quick question, do you have mods installed?

Many times unsupported mods will soft-fail leading to lag, bugs, and save file breaks.

[catloaf]

I do... But most (correction: all) of these mods are visual so I don't think they could damage a save. As for the crashes, I was referencing one's that have happened in pure stock installs. It's actually been crashing less now that I know what causes the crashes. Also some of these crashes were my pc's fault not 1.10's. I was more ranting about how unstable this update is in general. But I will take your advice and uninstall the mods if I'm doing something in a save I care about. Although is nice to know that incomparable mods seem to be the cause of minor annoyances with lag. 

Edited July 8, 2020 by catloaf
Thank goodness that saves at not in stored in 1 file like on console.

[catloaf]

Ok, so I have done more research and it turns out saving on the ksc screen is a really stupid thing to do. I already knew this, but though it only applies to the console versions. Now I know better.

But once again. I have been doing this since 2015 with no issues ever.

Edited July 8, 2020 by catloaf

[Vanamonde]

Moved to modded support. 

[VoidSquid]

  On 7/8/2020 at 9:40 PM, catloaf said:

Ok, so I have done more research and it turns out saving on the ksc screen is a really stupid thing to do. I already knew this, but though it only applies to the console versions. Now I know better.

But once again. I have been doing this since 2015 with no issues ever.

Expand  

I'm doing this for years, zero issues, incl. KSP 1.10, my last save before quitting is always from the KSC.

[catloaf]

  On 7/13/2020 at 4:21 PM, VoidSquid said:

I'm doing this for years, zero issues, incl. KSP 1.10, my last save before quitting is always from the KSC.

Expand  

I think it's a rare chance of happening in all versions, but more likely in less stable installs (console or modded.)