Please describe your issue in as much detail as possible:
The Steam Controller (2026) works everywhere inside Steam, but a game never receives input while the client runs as the experimental SteamRT3 client. Turning that off makes it work, and I can flip between the two states.
I run FINAL FANTASY XIV via XLM compatibility tool, which starts XIVLauncher.Core and runs the game with its own wine build and DXVK. Proton games are unaffected and work either way.
Steam's side looks healthy while the game is running with the toggle on:
/proc/bus/input/devices contains "Microsoft X-Box 360 pad 0", so the virtual gamepad is being created.
controller.txt shows "Queueing activation for controller: 0 app: 39210" (FINAL FANTASY XIV), not just 413080, so Steam Input engages the game's config.
The game sees an Xbox controller, but doesn't detect button presses. I have a virtual menu on left touchpad with keyboard presses, those work.
Controller: Steam Controller (2026), firmware current, connected wirelessly through the charging puck (28DE:1304, serial FXB99602002E2).
No difference from: the Steam client beta or STEAM_COMPAT_RUNTIME_SDL2=classic on the game.
Your system information
Please describe your issue in as much detail as possible:
The Steam Controller (2026) works everywhere inside Steam, but a game never receives input while the client runs as the experimental SteamRT3 client. Turning that off makes it work, and I can flip between the two states.
I run FINAL FANTASY XIV via XLM compatibility tool, which starts XIVLauncher.Core and runs the game with its own wine build and DXVK. Proton games are unaffected and work either way.
Steam's side looks healthy while the game is running with the toggle on:
The game sees an Xbox controller, but doesn't detect button presses. I have a virtual menu on left touchpad with keyboard presses, those work.
Controller: Steam Controller (2026), firmware current, connected wirelessly through the charging puck (28DE:1304, serial FXB99602002E2).
No difference from: the Steam client beta or STEAM_COMPAT_RUNTIME_SDL2=classic on the game.
Steps for reproducing this issue: