kerbal space program xbox one controller mapping

This issue extends beyond Unity and Rewired:

Just how they are doing this I do not know at this point and their implementation is flawed because it has problems supporting more than 2 controllers simultaneously. After working with the 360 pad's HID data myself, I'm certain that Unity hacked in special case code for the Xbox 360 pad and is somehow getting the data from some other source than the USB HID report (probably the USB device directly, essentially making their own driver) because that data is simply not separable. Interestingly, up until a certain version Unity's input system also did not separate these and you can see they added 2 extra axes to the controller (8 and 9) in a later version that separated the axes though they don't always work according to my tests and other's tests depending on which Unity joy id the controller shows up as. XInput is able to treat these axes as separate and detect simultaneous presses, but Direct Input and Raw Input are not. There is one single byte for the combined axis 0x00 -0x FF, with 0x80 being at rest. This is the way MS chose to expose the data in the HID report of the gamepad.

It sounds like you've disabled XInput, because unless you're using XInput on Windows, the two triggers on the X360 gamepad act as a single axis making it impossible to press both simultaneously. Click to expand.Short answer: Enable XInputīumper Bottom being the Triggers? And I'm guessing this is an Xbox 360 gamepad then.

Kerbal space program xbox one controller mapping