Tweakscale vs 1.12.3: will it kill my save?

[Hyperspace Industries]

I saw the warning, but, I'm asking this because we're going on vacation tomorrow and we don't have uncapped wifi where we're going, I want to know if the new 1.12.3 changes will break my saves.

[Lisias]

1 hour ago, Hyperspace Industries said:

I saw the warning, but, I'm asking this because we're going on vacation tomorrow and we don't have uncapped wifi where we're going, I want to know if the new 1.12.3 changes will break my saves.

Probably not, I made some superficial tests early this morning. I was more worried about KSP-Recall trying to fix something that was fixed on this release, but by my dismal,  it didn't. All known bugs handled by Recall are still there.

However, I didn't played too much on 1.12.3 and the latest TS, and besides the KSP change log is not saying anything that could worry me, it's possible that something hidden may jump and bite our SAS.

I would advise to keep constant and frequent backups of your savegames as you play - better safe than sorry. At least on the first few days. 

I will not have time to really pass through every TS feature on KSP 1.12.3 before Thursday at least.

Edited December 14, 2021 by Lisias
Hate autocompletes

[jimmymcgoochie]

I would caution against trying to update the base KSP version while you have mods installed in it- better to make a new copy of KSP in the new version and then copy your mods and saves across to it, that way if it all goes wrong you still have the original to fall back on.

[Hyperspace Industries]

17 minutes ago, jimmymcgoochie said:

I would caution against trying to update the base KSP version while you have mods installed in it- better to make a new copy of KSP in the new version and then copy your mods and saves across to it, that way if it all goes wrong you still have the original to fall back on.

Yeah, I just opened steam to check my play hours for fun and forgot to cancel the update.  Fortunately I have multiple backup instances to fall back on. I did this sort of mod installed update for 1.12.2 and it worked.

Anyways, I'm thinking of using steam to move my install back to 1.12.2, at least for the vacation. Is that a good idea?

[Lisias]

39 minutes ago, Hyperspace Industries said:

Anyways, I'm thinking of using steam to move my install back to 1.12.2, at least for the vacation. Is that a good idea?

Keep both.

The problem with 1.12.3 is that it's shinning new, and historically new KSP versions caused so many problems are they fixed.

But this latest release appears to be small and punctual enough to break the chain, so there's a good chance that 1.12.3 will work fine. I just won't bet any valuable on it.  

[jimmymcgoochie]

First of all, don’t put mods into the Steam copy of KSP, Steam breaks stuff especially when mods are involved and doubly so when you update the game. Keep the Steam copy free of mods and just copy it when you want to make a new modded install.

Second, you’ll need to do some save file hacking to roll back from 1.12.3 to 1.12.2 as save files aren’t forwards-compatible (a save won’t work in a version earlier than it was last used in); most likely changing the versions from .3 to .2 will fix it, though the docking port changes may cause problems if you roll back.

Lastly, just use a backup if you have one. The less you mess around with hit, the fewer chances there are for something to get broken. Keep the 1.12.3 copy for later use, it won’t go anywhere in the meantime.

[Hyperspace Industries]

27 minutes ago, jimmymcgoochie said:

First of all, don’t put mods into the Steam copy of KSP, Steam breaks stuff especially when mods are involved and doubly so when you update the game. Keep the Steam copy free of mods and just copy it when you want to make a new modded install.

Second, you’ll need to do some save file hacking to roll back from 1.12.3 to 1.12.2 as save files aren’t forwards-compatible (a save won’t work in a version earlier than it was last used in); most likely changing the versions from .3 to .2 will fix it, though the docking port changes may cause problems if you roll back.

Lastly, just use a backup if you have one. The less you mess around with hit, the fewer chances there are for something to get broken. Keep the 1.12.3 copy for later use, it won’t go anywhere in the meantime.

Too late, already rolled back to 1.12.2, it worked perfectly (when I loaded 1.12.3 I jumped out as soon as I saw the tweakscale warning, thus, my saves worked). I've backed up my save file. Thanks for the help though. 

As for steam breaking stuff, I've had a steam install with mods for quite a long time now, I know it's reckless, but I have a full backup, nothing's gone wrong yet, and I like to see how long I've played.

[Lisias]

26 minutes ago, Hyperspace Industries said:

Too late, already rolled back to 1.12.2, it worked perfectly (when I loaded 1.12.3 I jumped out as soon as I saw the tweakscale warning, thus, my saves worked).

And THIS is exactly why I coded that Warning!!!

You saved my day, it's pretty good to know that something I did prevented a problem.

(RL™ is being really harsh this week - essentially, everything I'm coding today is causing problems!! )