'No controller detected' specifically when launched via Gamescope session.

Very weird and specific technical issue here:

I’m running Arch Linux and launching the game on my desktop (i3wm) everything works fine, Steam Controller detected, game plays great. Usually though I play games through a separate TTY session that I launch a dedicated Gamescope Steam session in. Doing this I get better performance, near-perfect frame pacing, HDR support, and better streaming to my TV downstairs.

For some reason, specifically only Deadlock, when launched through this dedicated Gamescope Steam session it just doesn’t detect that there is any controller connected at all. Options menu says ‘No controllers detected’. Despite this, I can hit the Steam button, see the overlay, even edit all my bindings and stuff, it’s just that the game doesn’t actually see the controller. If I change my bindings to strictly KB/M binds I can technically still play that way, but then I lose out on the ‘Game Actions’ and automatic button prompt labels.

Not sure what I can include here to help troubleshoot. I should mention that Deadlock is the only game I’ve ever seen this issue with. I play a ton of games in this Gamescope Steam session all the time.

Launched this way:

gamescope -W 3840 -H 2160 -r 120 --force-grab-cursor --steam --hdr-enabled --adaptive-sync -e -f – steam -gamepadui
Click to expand…

Well, this result is one of the first ones on Google now for ‘gamescope no controller detected’ and I seem to have found a decent workaround for now. The gamescope command above? Replace ‘-gamepadui’ with ‘-steamos3’ and it has started working:

gamescope -W 3840 -H 2160 -r 120 --force-grab-cursor --steam --hdr-enabled --adaptive-sync -e -f – steam -steamos3
Click to expand…