http://bugs.winehq.org/show_bug.cgi?id=60226 --- Comment #1 from lifeartas1@gmail.com --- Confirmed real-world impact + working workaround, and where the fix belongs. This Wine XInput bug (enumerate-connected-but-never-map-input) is the root cause of a shipped-game failure: Kingdom Come: Deliverance II 1.5.6 (Bluetooth Xbox) never receives input on Linux. The game's xinput0 stays connected: 0 despite Wine XInput reporting the controller connected; the permanently-zero button state means the game sees no input and never connects the pad. Reproduces across Proton Experimental, GE-Proton, and Wine Staging 11.13, with real Bluetooth Xbox (xpadneo) and synthetic uinput devices — so it is Wine XInput, not any single game. Workaround (bypasses XInput): present the Xbox as a native DualSense and use the game's separate, working Sony HID (scepad0) path: InputPlumber ds5 UHID target + DisableHidraw=0 in the prefix. KCD2 then logs m_ControllerType: DualSense and input works. Details on Proton issue 8727. Suggested fix location: the fault is in Wine's XInput backend not feeding HID/evdev events into the returned XINPUT_STATE. Relevant code: dlls/xinput1_3/xinput_main.c / dlls/xinput1_3/xinput_hid.c and the bus enumeration in dlls/winebus.sys (unixlib.c) plus dlls/hidclass.sys. The controller IS enumerated (XInputGetState returns SUCCESS, packet increments) but XINPUT_STATE.Gamepad is never populated from the device's incoming HID/evdev reports. A dev would need to verify the HID report path from winebus.sys → xinput_hid.c for a Bluetooth (xpadneo, hid_xpadneo) device — the SDL path works but the native HID/evdev mapping into XINPUT_STATE does not. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.