Test Drive Unlimited Solar Crown
UPDATE 5: Updating to Preview fixes those problems. It likely has to do with outdated GPU drivers.
Out of curiosity to any Proton developers here, but what was needed to get the game running? (Looking around, I noticed that an override for xinput was added for this game).
Also, just saying, but the crash reporter showing up every time after exiting is the only issue remaining with this game.
Also, just saying, but the crash reporter showing up every time after exiting is the only issue remaining with this game.
That's an issue with the game as this also occurs on Windows.
Checking in to see if anyone has had a similar issue with the lighting bugging out? If I enable HDR it looks better albiet super washed out.
[1249970] Test Drive Unlimited Solar Crown - No controller input recognized with any controller (Proton 9/10/GE)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/9519.
@Xay0nara posted on 2026-02-23T14:19:32:
System Information:
• Steam AppID: 1249970
• Game: Test Drive Unlimited Solar Crown (TDUSC)
• OS: CachyOS Linux (64-bit)
• Kernel: 6.19.3-2-cachyos
• Desktop Environment: KDE Plasma 6.6.0 (Wayland)
• CPU: 13th Gen Intel® Core™ i5-13600KF (20 threads)
• GPU: AMD Radeon RX 7900 XTX
• RAM: 64 GiB (62.6 GiB usable)
• Motherboard: ASRock Z790 Steel Legend WiFi
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:
- Added
DisableHidraw=1toHKEY_LOCAL_MACHINE\System\\CurrentControlSet\\Services\\winebus(dword:00000001) - Attempted with clean prefixes after each major change
- Verified registry key persistence after Steam restart
System Configuration:
- Verified user is in
inputgroup (groups $USERshowsinput) - Installed
game-devices-udevpackage - Verified
/dev/input/js3permissions:crw-rw-r--@ 13,3 root input - Loaded
xpadkernel module manually (sudo modprobe xpad) - Disabled Steam Overlay (Properties → "Steam Overlay" unchecked)
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_descriptor error 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:
- Controller visible and responsive in
jstest-gtkon/dev/input/js3 - No
SDL: Detected joystick:entries in any Proton logs - No
XInputOpenDevice:entries in logs fixme:xinput:pdo_pnp code 0xc, not implemented!appears consistently across all Proton versions- Game launches successfully with keyboard/mouse, suggesting SARD Anti-Cheat allows execution but may block input device access
- Issue persists across kernel 6.19.2 and 6.19.3
Conclusion: 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.
Proton versions
proton 9.0-4x1 2026-02
Launch options
PROTON_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
Upstream links
- ValveSoftware/Proton/issues/9519x1 2026-02
Compatibility Report
System Information
I confirm:
Symptoms
The game seems to exhibit visual issues on my Steam Deck. Haven't tested on my main PC yet.
On my Steam Deck in the menu, it will randomly flash black rapidly .
In game, visual corruption can be seen in things like viewing maps. The same corruption occasionally happens when say being near a race location. The corruption primarily affects menus.
UPDATE: I just had a GPU hang while entering a race 22 minutes in.
UPDATE 2: I exited the game and it gave a crash report screen. Happens consistently
UPDATE 3: I can get the game to consistently GPU hang my Steam Deck by trying to enter into a race.
UPDATE 4: It no longer GPU hangs during races, but I still have those minor visual issues (like a "TV static" effect that appears around menus and occasionally 3D models every here and there) and the game crashing when exiting.
Reproduction