Camera movement/controls locked and unresponsive ONLY when controlling active vessel or viewing KSC - TEMP WORKAROUND / FIX

[bivouac]

This bug ONLY occurs when at the KSC or when you're otherwise in control of a vessel. I can move the camera around just fine in both the VAB and tracking station. I've heard of some people having issues in the VAB, so I want to reiterate that this DOES NOT apply to that issue. 

Excruciating detail for the devs (if they see this) since this one seems rather uncommon but can be reliably and repeatedly induced if affected by it

More or less, the camera appears locked in position once you're on the launch pad, in space, or at the main KSC view/selection menu. (Whatever you want to call it when you click return to space center.) After holding down RMB and applying constant movement to the mouse, maybe once every 5 seconds or so you'll notice the camera move, like, maybe 3mm. That's not an exaggeration. This also holds true when hitting tab and trying to see is mouse-look works. Nada. It's worth mentioning that snap still works just fine. "v" will still snap to the different view angles just fine, but you still won't be able to move the camera. When flying though, if I go into the map view, I can still move the camera around there. Transition back to vessel view, nada.

After some fiddling, I figured out what was causing the problem. It's probably worth mentioning that I play A LOT of light sims like DCS and MSFS, and normally would have somewhere in the range of about 9 or more separate devices plugged into my desktop at any given time. I only mention that because the only other people I've found who also experienced this exact issue also have a fairly notable amount of flight sim hardware that isn't of the Thrustmaster or Logitech variety or just a joystick and base. Thus far, I have yet to run into any deviation from that factor.

Source of the issue and quick/temp fix:
For whatever reason, KSP2 wasn't playing nice with one specific panel. If it matters, it's the Winwing Super Taurus F-18 dual throttle and startup panel. They're attached to each other, but the panel and throttle have their own respective USB ports independent of one another. My issue was specific to the startup panel only. The second I unplugged the startup panel, the camera suddenly snapped into position and I was able to move it freely around the launch pad/KSC view/vessel again. I tried plugging it back in to see if the problem would occur again, aaaand it did. I have absolutely nothing bound to any of my peripherals in the game. I only play it with mouse and keyboard. (First started playing in 2012. Old habits die hard.) Windows reads all of the different devices I have as game controllers and I can say with certainty they're not something that's just emulating keyboard keys/presses. Most other games will read them as a standard joy0_0 or joy2_[whatever button/switch input pressed] , so nothing surprising there. It also didn't matter if the software for calibrating/adjusting the controls was running or not.

That panel has over something like over 20 separate switches and most of those are 3-position, so maybe there was hard ceiling for inputs per device. However, one of the other people I came across said that it was only occurring with his Virpil throttle, which is well under that amount. I have a couple of other peripherals that are comparable to the problem one as well (though mostly multi-pos rotary switches rather than just switches), yet there's zero issue with them still being plugged in. Maybe just to spitball a couple possibilities: A) There's some threshold with either a max total number of inputs across all devices cumulatively, or total # of USB devices that once you go over it, the camera is the thing that bugs out for some reason. Might be something stuck in a loop trying to check some input that it couldn't assign but reads as pressed. B) I didn't see any option for it in the settings menu, but if the game isn't blanking  out or freezing panel/control states once you're loaded in and in control of the vessel (i.e. - ignoring whatever position they're in until they register a change), there's possibly some combo or specific problem child that the game can't make heads or tails of. Regardless of whether or not any controls have been assigned to that device. In either case, why only the camera is affected when viewing outside in general is its own mystery. Though it's probably safe to say that the KSC view is using the same block of code that the vessel view is using. 

[delenda]

I have the same issue although it only manifests for me once I alt-tab out of the game. A save and an exit to main menu then a reload _sometimes_ fixes it but more often than not, a game restart is needed.

Would be great to get this fixed as I don't want to have to disconnect things (and potentially lose joystick bindings) just to play KSP2. This bug has stopped my KSP2 playing dead in its tracks