Crew roster bugs are messing up my game, even after an attempted fix and a re-install (64bit)

[Cybindis]

So I recently had some lesser Kerbals die after an SSTO discombobulated itself shortly after re-entry sending it into an irrecoverable flat spin, but that's not a problem, I can just hire more Kerbals and/or load a quicksave. However it's what happened after is my issue. I could enter one building but never leave, after browsing the forums I discovered Claw's fix of modifying my persistent files so that conflicts can't occur. I did this however it only partially worked. I can enter the Kerbal lounge, and only the kerbal lounge. I can exit it, but when I do I get stuck in KSC and I can't quit to main menu or select any menu options. This is after a fresh install with a changed .sfs

Any help would be greatly appreciated. It'd suck to go from doing what I want to be doing, which is designing using and modifying SSTOs into something useful apart from a bus system into LKO, to having to do another fresh install and start again and get those ....... upgrades to the VAB and SPH which make them meaningful (This run-through I had every science object researched with ~2500 science and was still knocking about 750,000 monies).

[Seaview123]

I'm with you, man. I was just about completed with the tech tree when I had an unfortunate accident which killed a bunch of my Kerbals. One of the casualties was a Kerbal I'd gained through one of those "Rescue from Orbit" missions. (Also, I'd fired Jeb, Bill, and Bob. They were prima donnas and were hogging too much of the spotlight.) The next time I returned to the Space Center I started seeing this bug.

I read through Claw's tutorial, but it looks like the Kerbal "Three Amigos" aren't just fired... they disappeared from my persistence.sas file. Unfortunately, there's a bunch more things wrong with my persistence and quicksave files, too (like completed contracts missing, and others with pointers showing Jeb doing stuff, etc.).

I decided rather than get a "Unity reprogramming for Dummies" book and devote countless hours to repairing strange software bugs, it would let me play more KSP if I just started a new career. I copied the .craft files from my previous Save folder, cheated myself a bunch of money and science, and am in the process of rebuilding my world. This time I'll just make sure I don't fire Bill/Bob/Jeb, and not let any rescued Kerbals ever fly again.

If anyone has suggestions for fixing my old career without digging through 3 million lines of code, please let me know.

[Cybindis]

I'm with you, man. I was just about completed with the tech tree when I had an unfortunate accident which killed a bunch of my Kerbals. One of the casualties was a Kerbal I'd gained through one of those "Rescue from Orbit" missions. (Also, I'd fired Jeb, Bill, and Bob. They were prima donnas and were hogging too much of the spotlight.) The next time I returned to the Space Center I started seeing this bug.

I read through Claw's tutorial, but it looks like the Kerbal "Three Amigos" aren't just fired... they disappeared from my persistence.sas file. Unfortunately, there's a bunch more things wrong with my persistence and quicksave files, too (like completed contracts missing, and others with pointers showing Jeb doing stuff, etc.).

I decided rather than get a "Unity reprogramming for Dummies" book and devote countless hours to repairing strange software bugs, it would let me play more KSP if I just started a new career. I copied the .craft files from my previous Save folder, cheated myself a bunch of money and science, and am in the process of rebuilding my world. This time I'll just make sure I don't fire Bill/Bob/Jeb, and not let any rescued Kerbals ever fly again.

If anyone has suggestions for fixing my old career without digging through 3 million lines of code, please let me know.

I recently had to reformat and swap out hardrives on my PC because my old one crapped out on me, so I had to start again... again.. again..

Now this time I've started an interstellar mod career for something to do until a solution is found. But I'd rather not start totally again. Again.