My world will not let me go into the sph or the vab, tracking station, etc.

[FSXPRO5]

I was going to go in the SPH but it wouldnt let me go in there. Is it possible that my game files are corrupted? I transferred the files from my world to a new world that I created and the same this happened in that world. Plz help me.

[monstah]

If you think the files are corrupted, you can try reinstalling the game (or, if you've downloaded through Steam, there's the option to "Verify game files integrity", or something like that, that will search for corrupted files and only download those).

In any way, what do you mean by a "world" here, and what files did you move?

[FSXPRO5]

4 minutes ago, monstah said:

If you think the files are corrupted, you can try reinstalling the game (or, if you've downloaded through Steam, there's the option to "Verify game files integrity", or something like that, that will search for corrupted files and only download those).

In any way, what do you mean by a "world" here, and what files did you move?

i moved my craft files.

[monstah]

Oh, so you started a new save and copied the craft files from the old save? Okay then.

Yes, sounds like its something in the game and not the save game. I highly doubt a problem on a ship file would corrupt the KSC scene. My best guess is that you're using a mod that's not compatible with the KSP version you're playing. What version are you playing, and what mods are you using?

 

[FSXPRO5]

44 minutes ago, monstah said:

Oh, so you started a new save and copied the craft files from the old save? Okay then.

Yes, sounds like its something in the game and not the save game. I highly doubt a problem on a ship file would corrupt the KSC scene. My best guess is that you're using a mod that's not compatible with the KSP version you're playing. What version are you playing, and what mods are you using?

 

I am playing on 1.3 . I have many mods, but none of them are incompatible. It was working with all the mods before but i closed the game and reopened it and that is when it didnt work. 

[monstah]

Yeah, sorry but I have no idea here. Hope someone else can help you  

[SpannerMonkey(smce)]

1 hour ago, FSXPRO5 said:

I was going to go in the SPH but it wouldnt let me go in there.

Hi, In KSC view  press alt F12 from the window appears in the column on the left click input locks,  in the section that opens select clear input locks.

AltF12 again and all should be well , normal service should be resumed.

It's worth adding that I'm seeing lots of reports of this input lock business, all over the place, and can honestly say before 1.3 it happened to me,  maybe twice in the entire time i've been playing KSP (since 0.16), it's happened 5 times today . so it's a good job the fix is easy 

Edited June 6, 2017 by SpannerMonkey(smce)

[FSXPRO5]

21 minutes ago, SpannerMonkey(smce) said:

Hi, In KSC view  press alt F12 from the window appears in the column on the left click input locks,  in the section that opens select clear input locks.

AltF12 again and all should be well , normal service should be resumed.

It's worth adding that I'm seeing lots of reports of this input lock business, all over the place, and can honestly say before 1.3 it happened to me,  maybe twice in the entire time i've been playing KSP (since 0.16), it's happened 5 times today . so it's a good job the fix is easy 

I clicked clear input locks and it didn't work.

[monstah]

54 minutes ago, SpannerMonkey(smce) said:

Hi, In KSC view  press alt F12 from the window appears in the column on the left click input locks,  in the section that opens select clear input locks.

AltF12 again and all should be well , normal service should be resumed.

It's worth adding that I'm seeing lots of reports of this input lock business, all over the place, and can honestly say before 1.3 it happened to me,  maybe twice in the entire time i've been playing KSP (since 0.16), it's happened 5 times today . so it's a good job the fix is easy 

Wow, I've had such a problem happen to me once or twice before in almost 2000 hours of game time. I had no idea a) it was so easy to fix and b) it was so common now in 1.3. Thanks for this!

edit - Although, it didn't work for the OP.  

Edited June 6, 2017 by monstah

[SpannerMonkey(smce)]

Just now, monstah said:

Wow, I've had such a problem happen to me once or twice before in almost 2000 hours of game time. I had no idea a) it was so easy to fix and b) it was so common now in 1.3. Thanks for this!

No worries, pity it didn't work for the OP's problem, which sounds horribly like a corrupted save , given that input lock wasn't the problem.

[monstah]

Just now, SpannerMonkey(smce) said:

No worries, pity it didn't work for the OP's problem, which sounds horribly like a corrupted save , given that input lock wasn't the problem.

He mentioned starting a new save and just moving over the ship files already

You know what, could be a corrupted settings file for a mod. I've had similar problems when some mod makes an "invisible window" on the screen, a region of the screen where if my mouse goes over it the input is locked as if a pop-up was there. I've think it's KER that does it, but I'm not sure. Resetting window positions on mods could help (see which mods have either settings on the stock toolbar or the advanced settings menu, and if any of them has some sort of "reset window positions" button you can access).

 

Other than that, all I can think of is trying all the mods. I've done it before on a game with some 70+ mods, it was boring as heck but it worked at least. The way I did it is this:

1. create two "quarantine" folders somewhere outside GameData, one for "testing" mods and another for "OK" ones.
2. Move half your mods to the "test" folder.
3. Check the mods that are left, if any of them requires a mod you just quarantined. If so, quarantine them, too.
4. Open KSP, see if problem persists.
5. If problem persists, problematic mod is still installed. Move the mods from the "test" to the "OK" folder, and repeat 2-4
6. If game works fine, then problematic mod is in "testing" folder. Repeat the process, but now add those mods back to the game.
7. Finally, when you found the guilty one, move everything from the "OK" folder back to GameData and see if it indeed does work.

If you find a more efficient workflow, I'd like to know!

[HvP]

There is an old problem that had symptoms similar to this. As I recall it had to do with Kerbals being fired in the Astronaut Complex after being declared MIA. Basically the available crew roster no longer matches the progress tracking of those crews for contracts.

That thread describes how to change the persistence file to bring the affected Kerbal back to life.

Edited June 6, 2017 by HvP