

accelerating if trigger is not pressed) and swapped (mapping LT to acceleration makes it brake and vice-versa). When I play, mapping seems inverted (e.g.

Before, I could map combined accelerate & brake controls by pressing LT (recognized as Z-axis), now LT & RT work separately as Z-axis and Z-rotation. Worked fine in Win 7 with drivers from the website (never downloaded automatically for me) until I upgraded.

Both triggers are inverted and full range, not zeroeing out properly or something like that. There is also a "Controller 2", where it doesn't detect any associated controller, but it responds correctly to my inputs.ĭisabling the "XINPUT compatible HID device" device in the Device Manager makes it so "Controller 1" is the "phantom" controller that works, but it still only works on x360ce - trying it on an actual game doesn't show the controller, as it is invisible.ĮDIT2: Uninstalling and letting it install the "XINPUT compatible HID device" made it so that any input (on either trigger) would show up as left trigger 111 on x360ce on the "Controller 2" tab (wtf) There is a "Controller 1", which is the one it detects as the "XBOX One for Windows" controller, and it has both the left and the right trigger stuck at 255 (max). (Code 19)".ĮDIT: Opening x360ce to test the controller gives even more bizarre results. triggers don't work at all on FFXIV), but letting it pick drivers automatically picks the one that has "Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. Using the update driver screen and manually picking the 6.2 drivers makes it "work", although it is broken in some games (e.g. This mysteriously started happening to me a few days ago too :(
