![controller xinput support test controller xinput support test](https://i.ytimg.com/vi/7OmKi444Dak/maxresdefault.jpg)
Below we show you how to make your X-Arcade controller work as an Xinput device or DirectInput device on PC. Xinput works with both Xinput games and most DirectInput games, so we recommend it. But some newer games, such as Killer Instinct, Mortal Kombat X, Street Fighter IV & V, and Steam, require the newer Xinput protocol that was introduced with the Xbox 360 gamepads (and now Xbox One). The original way for an input device to work as a gamepad was through the DirectInput protocol, which still works on the vast majority of gamepad-enabled games.
![controller xinput support test controller xinput support test](https://img.itch.zone/aW1nLzM0MzkxOTIucG5n/original/r58HBm.png)
Thank you.While the X-Arcade controllers work as a keyboard with the default PC connection, there are ways to make it act like a gamepad instead for games that don't offer great keyboard-based controller support. I really do appreciate you taking the time to step through all this with me. it's looking a lot like a possible bug in Emulation Station maybe? I've seen identical behavior using both xpad and xpadneo (so far).The the triggers work within retroarch when I manually edit a config file.jstest recognizes the triggers when pressed.xpadneo identifies and drives my controller.Jul 12 08:31:24 lvl2: /opt/retropie/supplementary/emulationstation/scripts/inputconfiguration.sh Jul 12 08:31:24 lvl3: fireEvent: controls-changed Jul 12 08:31:24 lvl3: fireEvent: config-changed Jul 12 08:31:24 lvl2: Mapping -> HotKeyEnable
![controller xinput support test controller xinput support test](https://4.bp.blogspot.com/-EEGCPlSKL8s/V9eHFd6VF9I/AAAAAAAAMwU/WVIOnC9VoJEdsqAOuADY4pV3_qsoC-udACLcB/s1600/Disconnect.jpg)
Jul 12 08:31:23 lvl2: Mapping -> RightAnalogRight Jul 12 08:31:23 lvl2: Mapping -> RightAnalogLeft Jul 12 08:31:22 lvl2: Mapping -> RightAnalogDown Jul 12 08:31:22 lvl2: Mapping -> RightAnalogUp Jul 12 08:31:21 lvl2: Mapping -> LeftAnalogRight Jul 12 08:31:20 lvl2: Mapping -> LeftAnalogLeft Jul 12 08:31:20 lvl2: Mapping -> LeftAnalogDown Jul 12 08:31:19 lvl2: Mapping -> LeftAnalogUp Jul 12 08:31:06 lvl2: Mapping -> RightShoulder Jul 12 08:31:06 lvl2: Mapping -> LeftShoulder Jul 12 08:30:58 lvl2: Configuring device 0 (8Bitdo SN30 Pro). Jul 12 08:30:51 lvl3: SystemView::getViewElements() Jul 12 08:30:51 lvl2: Added known joystick '8Bitdo SN30 Pro' (instance ID: 0, device index: 0) Instead, there's nothing in the log about triggers at all, and indeed the UI gave no indication that any button or trigger was being pressed at that time. I've noted the first line about "buggy firmware," but I'm already running the latest 8Bitdo firmware available (2.02) so I'm not sure what that's looking The ES debug log seems to indicate that ES isn't seeing the triggers being pressed at all.Īfter " Mapping -> RightShoulder" when I was asked to press the left and right trigger buttons, I made sure to press L2 and R2 ten times each so they would be obvious in the log before I did a "hold button to skip" to move on. xpadneo 0005:045E:02E0.000A: enabling compliance with Linux Gamepad Specification xpadneo 0005:045E:02E0.000A: fixing up report descriptor size xpadneo 0005:045E:02E0.000A: pretending XB1S Windows wireless mode (changed PID from 0x02E0 to 0x028E) I start with the controller off, then power it on and this is the output I see as soon as it connects: xpadneo 0005:045E:02E0.000A: buggy firmware detected, please upgrade to the latest version