1.02 save breaks 1.03 VAB

[g00bd0g]

Opening my 1.02 save in 1.03 results in bizarre VAB behavior where I can't click on anything. Can only exit back out.

[sal_vager]

Always back up saves, just in case, but please upload your saves to dropbox as I was able to load all my 1.0.2 saves with no issues, I may be able to load yours and fix it.

[basic.syntax]

I had a problem that sounds like this.

I couldn't select parts in VAB. Parts categories buttons were partially displayed, and not functional. Not fixed by restarting KSP.

Was fixed for me, by exiting KSP, and starting a new game. All the parts and buttons were working.

Then I reloaded my older career game, and all the parts and VAB buttons were working again.

[Jon144]

Same problem here. There was no warning that 1.0.3 would break saves... Since you marketed it simply as a bug-fixing patch. All it did was create more. In my experience at least.

[Mister Dilsby]

Am working this now. Moved the Kerbfleet save into 1.0.3... VAB broken, picture just like Jon144's. Then removed all mods except KER (I have ships with the Engineer Chip part, so this is a must-load on that save), reloaded, and it's fine. Will start adding mods back now and see what happens...

ETA: All mods loaded (KER, Alarm Clock, Boulder/EVE) and it's fine. Now will start moving some ships into the VAB and see what happens.

Edited June 24, 2015 by Kuzzter

[Mister Dilsby]

Ok, I moved some ships in and it was fine. Edited a ship but did not launch. Turned off the game--loaded this morning and VAB is broken again. Not sure what to do here.

[Padishar]

Not all saves suffer from the problem and it only happens if you haven't loaded a working save in this session of KSP. Loading a working save (or starting a new one) seems to correctly initialise something in KSP so it is then be able to load the bad save.

We will need an output_log.txt/player.log file of a run where the VAB has problems and (preferably) the save file you loaded that had this issue. The more examples of bad saves that we can give to the developers, the easier it will be for them to track down the problem and fix it.

[Mister Dilsby]

Thanks--cannot get those files fro where I am but did find another thread where sal_vager said that the IRL pointing to the tech tree could get corrupted by module manager. This makes sense, as I did move mod folders in and out of the new install when I moved the save.

Will try editing .sfs to point to the correct tech tree, and will report back a bit later.

[Mister Dilsby]

OK here we go... I looked in persistent.sfs and found this:

CAREER {

TechTreeUrl = GameData\ModuleManager.TechTree

Per sal_vager's recommendation here am changing to "TechTreeUrl = GameData/Squad/Resources/TechTree.cfg" and starting up...

YES! VAB works... or should I say' date=' my save has been sal_vaged![/color']