jamis

Thank you! Clearing the input locks allowed me to regain control of the craft and the interface. I still haven't figured out what triggers this condition, but at least clearing the input locks gives me a workaround. - Jamis

This happens to me as well. I haven't yet figured out how to reliably duplicate it, but it happens often enough to be frustrating. The only way out is to "cmd-Q" and restart the game. Some notes: I've only noticed it happening when I have the orbital info active. That could be a red herring, though, since I have that mode open far more often than the others. The F* keys works as usual (I can hide UI, show mission stats, etc). Other keys have no effect (including escape, z, x, shift, control, wasd, t, etc.). The other tabs for the flight modes (the ones that let you switch between staging view, orbital info, view, etc.) are darkened and disabled; clicking them has no effect. The game continues to play -- engines continue to burn, craft continue on their preexisting trajectories, etc. -- but no input is recognized. I've attached a screenshot from the latest incident. I was in the middle of maneuvering the rocket, pressing the usual keys (WASD, shift, control, arrow keys), but I don't recall if there was a particular combination of keys that caused it. You can see the tabs in the lower left are darkened. You can see that the probe has a network connection and ought to be controllable. The electricity resource is not pictured (because the UI at this point was unresponsive) but the probe had plenty of electricity. If/when it happens again I'll try to post more information to help diagnose. This is really getting frustrating. Thank you! - Jamis Edit: this is in KSP 1.7.1, on macos 10.14.5, on a 2015-era 15" MacBook Pro with retina display.

In the interest of saving others some headache, I relate the following. I recently tested the warp drive out successfully on a smaller ship, and then--confident that I could make it work like I wanted--built a warp "tug" and docked a bunch of things to it, and sent it to Eeloo. The mission was a wild success, but when I tried to bring it home, the ship would explode upon entering Kerbin's SOI at warp. I tried auto-strutting all the things, I tried undocking bits I could (just barely!) live without, but all to no avail. I could not seem to enter Kerbin's SOI (at warp) without the ship exploding. Almost by chance, I tried entering the SOI obliquely, barely intersecting the sphere, almost at a tangent, and it worked just fine. So, if anyone out there ever encounters this situation, perhaps try entering the SOI at a tangent?

I apologize if this has been addressed before. I looked through much of this thread but didn't see anything that seemed relevant. For any world with atmosphere, I'm seeing the following visual glitch when within some distance from the surface: Again, this happens with Kerbin, Eve, Laythe, Jool, and Duna. Anything with atmosphere. I'm on a Mac (last year's 15" MacBook Pro), using these CKAN-installed mods: I will try paring away mods to see what fixes it, if necessary, but I wanted to see if anyone else has seen this, and if there might be an obvious fix for it. Thank you! I love what I've seen so far with SVE, but that atmosphere glitch is a real kill-joy. :/