No controller input

[kaysur]

I set up gamescope on Fedora and when launching a game with it I have no controller input, however when using the -e flag I have controller input.
gamescope wiki implies this is for Steam integration, so is this somehow related to controller input working? I don't have Steam Controller Input enabled for my games, so this doesn't make sense to me.
I think this flag should be properly documented in the wiki and README with other flags because I already gave up on troubleshooting gamescope on one day and knowing this would have helped.

[aqxa1]

I have the same issue, but the workaround isn't needed for all games, so it might just be an incompatibility with the particular game. E.g. it's broken with Chrono Trigger but not Desperados III or Ion Fury. Possibly a Proton issue given both of the working games are native releases.

[kaysur]

#420
Looks like this could be related. First report says mouse works in Proton experimental, but not 7.0-1, so when I play another round of Hades or something I can also try that.

[AtilaSaraiva]

It doesn't even work here with the -e option. I'm using the flatpak steam version with NixOS as the OS.

[Holzhaus]

I had the same issue with Rise of the Tomb Raider. When running it via Proton 7.0-1, mouse and controller input works, but when using gamescope, both mouse and controller stop working (keyboard input still works though).

I confirm that adding the -e flag fixes the problem:

gamescope -W 1920 -H 1080 -e -- %command%

[cactushydrocodone]

Using the -e flag too, no controller input for me :/

In LEGO Star Wars: The Complete Edition, the touchpad works on the PS4 Controller. But nothing else. Really strange

Funny enough, if one did something like this:
gamescope -- alacritty and then runs jstest /dev/input/js0 inside the new window, the controller works perfectly.
So this must be a weird issue with gamescope in combination with steam.

[Holzhaus]

Just a note, I have Steam Input enabled (because I'm mainly playing via Steam Link).

@cactushydrocodone maybe check if you have Steam Input enabled for PS4 controllers?

[cactushydrocodone]

Just a note, I have Steam Input enabled (because I'm mainly playing via Steam Link).

@cactushydrocodone maybe check if you have Steam Input enabled for PS4 controllers?

Damn that helped! Now i can press any button, which brings me to the controller configuration thingy of the game which looks a bit funky:

Now, i cant press anything except the touchpad button anymore. :/

[cactushydrocodone]

Its not only LEGO Star Wars, none of the games i tested work.

[cactushydrocodone]

I FINALLY solved it.
It wasnt a gamescope problem, it was a steam problem!
I turned off the controller support for playstation and suddenly, it worked!

Those are my settings in steam now:

[opale95]

I have the problem on games ran with Proton at any higher version than 6.3-8.
Keyboard and Mouse seems to work, but not my Xbox360 wired controller.
Anything Steam Input related is disabled on my end (Globally and per-game).
I tried disabling Steam in-game overlay or launching games via Big Picture Mode with no luck.
I checked it was working fine without gamescope.

I'm running an updated Manjaro Linux system, DE is XFCE+i3, gamescope 3.11.28.beta2.
It works with the -e option which maybe was made for this kind of situations but i didn't find documentation about this except the wiki which wasn't clear.

[cactushydrocodone]

@opale95 -e is not documented but it is required for every proton version after 6.3. Just use it, it does not hurt ;)

[QushyQushy]

I have the same issue with the Neptune Controller on the Steam Deck. In HZD neither the DualSense or Neptune controllers work. In Cybeprpunk the DualSense controller works (even though no Playsation Controller compatibility is enabled in Big picture Mode) but the Neptune doesn't. This is the command I'm using:

gamescope -e -U -f -w 960 -h 600 -W 1280 -H 800 -- mangohud %command%

[inittux111]

I'm having the same issue with my mouse when using gamescope with Proton 7.x, so I was currently running al my games on Proton 6.3.8 where I wasn't have the issue. The solution mentioned here is to launch gamescope with the -e option, does anyone know what changed in Proton or gamescope that this option is needed?

@cactushydrocodone How did you find out that -e is needed for every Proton version after 6.3.x?