Hello @Xay0nara, we're using one issue report per unofficially supported game title, so I've gone ahead and transferred this issue report to https://github.com/ValveSoftware/Proton/issues/8157#issuecomment-3945058790.
proton 9.0-4x1 2026-02PROTON_ENABLE_GAMING_INPUT=1x1 2026-02PROTON_ENABLE_HIDRAW=0x045e/0x0b00,0x045e/0x0b13,0x045e/0xb22x1 2026-02PROTON_LOG=1x1 2026-02PROTON_NO_BWRAP=1x1 2026-02PROTON_NO_PRESSURE_VESSEL=1x1 2026-02PROTON_NO_XINPUT=1x1 2026-02PROTON_USE_XINPUT=1x1 2026-02SDL_GAMECONTROLLER_IGNORE_DEVICES=0x045e/0x0b00,0x045e/0x0b13,0x045e/0xb22x1 2026-02SDL_JOYSTICK_DEVICE=/dev/input/js3x1 2026-02SDL_JOYSTICK_HIDAPI=0x1 2026-02SDL_JOYSTICK_HIDAPI=0:x1 2026-02WINEDEBUG=+controller,+joystick,+xinputx1 2026-02WINEDLLOVERRIDES=xinput1_4,builtinx1 2026-02
System Information:
Proton Versions Tested:
• Proton CachyOS 10.0-20260207-slr
• GE-Proton 10-32
• Proton 9.0-4 (official Valve build)
Controllers Tested:
• Xbox Elite Series 2 (USB & Bluetooth)
• Xbox Series Controller
• Google Stadia Controller
Problem Description: Controller input is not recognized in-game while keyboard and mouse work perfectly. The system detects controllers correctly (visible in jstest-gtk with input events on /dev/input/js3), but Proton/Wine does not pass them through to the game. No SDL: Detected joystick: or XInputOpenDevice: entries appear in logs even with debug flags enabled. This affects all tested controllers and all Proton versions.
Reproduction Steps:
1. Connect any controller (tested with Xbox Elite Series 2 via USB, Xbox Series Controller, Stadia Controller)
2. Verify controller works in jstest-gtk and appears as /dev/input/js3
3. Launch Test Drive Unlimited Solar Crown with any Proton version
4. Navigate to controller settings or attempt gameplay
5. Controller inputs are ignored completely (no detection in game)
6. Keyboard and mouse input works immediately
Attempted Fixes:
Steam Input Configuration:
• Disabled Steam Input globally (Steam Settings → Controller)
• Disabled Steam Input per-game (Properties → Controller → "Disable Steam Input")
• Verified controllers appear in Steam Big Picture mode (they do)
Proton Launch Options (tested individually and in combination):
PROTON_USE_XINPUT=1
PROTON_NO_XINPUT=1
SDL_GAMECONTROLLER_IGNORE_DEVICES=0x045e/0x0b00,0x045e/0x0b13,0x045e/0xb22
SDL_JOYSTICK_HIDAPI=0
SDL_JOYSTICK_DEVICE=/dev/input/js3
PROTON_ENABLE_GAMING_INPUT=1
PROTON_ENABLE_HIDRAW=0x045e/0x0b00,0x045e/0x0b13,0x045e/0xb22
WINEDLLOVERRIDES=xinput1_4,builtin
PROTON_NO_BWRAP=1
PROTON_NO_PRESSURE_VESSEL=1
PROTON_LOG=1
WINEDEBUG=+controller,+joystick,+xinput
Registry Modifications:
DisableHidraw=1toHKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\winebus(dword:00000001)System Configuration:
inputgroup (groups $USERshowsinput)game-devices-udevpackage/dev/input/js3permissions:crw-rw-r--@ 13,3 root inputxpadkernel module manually (sudo modprobe xpad)Relevant Log Excerpts:
Proton CachyOS 10.0 - Initial XInput failure (without fixes):
00c0:fixme:xinput:pdo_pnp code 0xc, not implemented!
00c0:fixme:hid:build_joystick_report_descriptor More than 8 absolute axes found, ignoring.
00a0:err:ntoskrnl:ZwLoadDriver failed to create driver L"\Registry\Machine\System\CurrentControlSet\Services\winebth": c0000142
After applying DisableHidraw registry key and SDL_JOYSTICK_HIDAPI=0:
0094:00bc:fixme:xinput:pdo_pnp code 0xc, not implemented!
0094:00a0:err:ntoskrnl:ZwLoadDriver failed to create driver L"\Registry\Machine\System\CurrentControlSet\Services\winebth": c0000142
0090:009c:trace:loaddll:build_module Loaded L"C:\windows\system32\drivers\hidparse.sys"
0090:009c:trace:loaddll:build_module Loaded L"C:\windows\system32\drivers\winebus.sys"
(Note: The
hid:build_joystick_report_descriptorerror disappeared after registry modification, but controller still not detected. No SDL detection lines appear.)GE-Proton 10-32 - Windows.Gaming.Input attempt:
0170:fixme:combase:RoGetActivationFactory (L"Windows.Gaming.Input.Gamepad", {8bbce529-d49c-39e9-9560-e47dde96b7c8}, 000000000147C298): semi-stub
6660.834:0094:00bc:fixme:xinput:pdo_pnp code 0xc, not implemented!
6660.841:0094:00a0:err:ntoskrnl:ZwLoadDriver failed to create driver L"\Registry\Machine\System\CurrentControlSet\Services\winebth": c0000142
GE-Proton with Xbox Series Controller (same result):
6809.742:0094:00bc:fixme:xinput:pdo_pnp code 0xc, not implemented!
6809.756:0094:00a0:err:ntoskrnl:ZwLoadDriver failed to create driver L"\Registry\Machine\System\CurrentControlSet\Services\winebth": c0000142
6809.751:0094:00bc:fixme:xinput:pdo_pnp code 0xc, not implemented!
Proton 9.0-4 - Same behavior:
6809.739:0094:00bc:fixme:xinput:pdo_pnp code 0xc, not implemented!
Critical Observations:
jstest-gtkon/dev/input/js3SDL: Detected joystick:entries in any Proton logsXInputOpenDevice:entries in logsfixme:xinput:pdo_pnp code 0xc, not implemented!appears consistently across all Proton versionsConclusion: After exhaustive testing of all available workarounds (Steam Input settings, environment variables, kernel modules, udev rules, registry edits, sandbox disabling, and multiple Proton versions), the issue appears to be a fundamental incompatibility between the game's input handling/SARD Anti-Cheat and current Proton/Wine HID implementations on this system configuration. The pdo_pnp code 0xc error persists across all tested versions, suggesting incomplete XInput/Gamepad support for this specific title on CachyOS kernel 6.19.x.