No controller input for non-steam games with Switch Pro Controller

[szszoke]

Hello!

I am trying to run Steam in gamescope because things like big picture or in-home streaming works better (or at all). I use a Nintendo Switch Pro Controller.

I launch Steam like this:

gamescope -e -f -W 2201 -w 2201 -H 1080 -h 1080 -r 60 -- steam -tenfoot -steamos

This gets me a full screen Steam Big Picture window. At this point my controller is detected and I can use it to navigate the big picture UI. The controller also works as expected in games that I purchased from Steam. I tested with Cyberpunk 2077, Shadow of the Tomb Raider, Uncharted.

I also have some games from GOG.com that I installed via Heroic Launcher. Those games are added to Steam.

When I launch Steam directly (without gamescope) my GOG.com games also detect my controller.

When I launch Steam via gamescope however then launch one of my GOG.com games, they do not react to controller input. They still detect that a controller is connected (and detect a disconnection if I turn off my controller).

The Steam overlay works if I press the home button on my controller.

It might be that I am having the same issue as https://github.com/Plagman/gamescope/issues/502 or https://github.com/Plagman/gamescope/issues/502.

If I launch gamescope with the --debug-hud and --debug-events flags, I can see a lot of event 91 and at least in one game, Horizon Zero Dawn, if I load a level with mouse and keyboard, then turn on my controller, the game thinks I am holding the left trigger down.

[szszoke]

In the meantime I realized that my kernel (6.2) has built-in support for my controller so I blacklisted the ff_memory and hid_nintendo.

I did this to avoid conflicts between the kernel and the Steam controller drivers.

It didn't make a difference.

[Joshua-Ashton]

Gamescope has no relation to controller or gamepads in any way fwiw. Its likely the combo of flags you are passing to Steam that is causing an issue.

[szszoke]

If I run Steam directly with the same flags then my controller is working as expected.

steam -tenfoot -steamos

I think gamescope is still involved somehow.

[czak]

I am observing the same behavior.

My minimal test scenario:

1. Add xInput Controller Tester as a non-Steam game
2. Run Steam (either with or without Gamescope)
3. Force a Proton version under "Compatibility"
4. PLAY the ControllerTester.exe and observe gamepad input

Results:

• Steam run with Gamescope: gamescope -e -- steam -gamepadui
  • Proton 8.0-3 - Controller not working, mouse cursor hidden, mouse input not working
  • Proton 7.0-6 - Controller not working, mouse cursor hidden, mouse input not working
  • Proton 6.3-8 - Controller working, mouse cursor displayed, mouse input working
  • Proton 5.13-6 - Controller working, mouse cursor displayed, mouse input working
• Steam run directly, without Gamescope: steam -gamepadui
  • Proton 8.0-3 - Controller working, mouse cursor displayed, mouse input working
  • Proton 7.0-6 - Controller working, mouse cursor displayed, mouse input working
  • Proton 6.3-8 - Controller working, mouse cursor displayed, mouse input working
  • Proton 5.13-6 - Controller working, mouse cursor displayed, mouse input working

My reasoning: something is different between Proton 6.3-8 and Proton 7.0-6 and it affects the input handling or focus and it manifests itself when run inside Gamescope.

Some notes:

• None of this affects Steam games. Happily running Resident Evil 2 within Gamescope, with a controller, on Proton 8.0-3.
• None of this affects native Linux games added as non-Steam game. Tested with "Baba is You" from itch.io.
• My controller is Xbox One wireless via xpadneo
• Same results with gamescope in Wayland, and run from a virtual terminal

[DocMAX]

i have same issue. using gamescope makes my controller (ps5 bluetooth) not work. but it works without gamescope. also i am not able to click on buttons with mouse cursor.

[JoshElias]

Same issue here