-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
games not recieving controller input on wayland #782
Comments
Any additional details? How are you running gamescope? What hardware do you have? What game are you trying to run, and what settings? You can get hardware info by copying the info in the "About this System" and "Wayland Info Center" apps on the DE. I have a very similar setup and I'd like to try and replicate this issue. Try re-running the program w/ the same conditions using " --debug-hud" and "--debug-events" flags and dump the console output to a file and paste here. Hopefully those logs will help. |
I am running it throught the launch options like normal, I have yet to find a configuration of gamescope that does not have this issue. I usually just do 'gamescope -f -e %command%'. I have had this issue on both elden ring and cod black ops 3. |
Same issue here with Monster Hunter World and Sway. Here's the output of Hardware Information (from Steam)
Edit: As said in #822, running Steam itself through gamescope rather than a game itself makes controller input work. |
still have this issue also. |
I'm wondering if this is a input focus issue? I've noticed that controller input can make things happen in Steam, while the game is my focused window and receiving keyboard and mouse events. |
Some more testing seems to indicate this issue may be limited to games run via Proton. When I run Project Zomboid as a Linux native game, controller input is registered both with and without Gamescope. When forcing Steam to launch it via Proton Experimental however, controller input stops working with Gamescope, but continues working fine without Gamescope. update: To confirm this isn't a recent Proton thing, I was also able to produce this behaviour with Proton 7 |
not sure if im having the same issue, with a joystick on fedora 39, joystick is detected fine in the system and works great with flightgear, but isnt detected by basically everything else |
I'm having this issue also on wayland. I built gamescope myself so I'm on the latest version. |
I ran into this issue on Arch Linux (Wayland, Plasma 6, AMD CPU and GPU) trying different games (e.g. No Straight Roads, Marvel's Avengers, Gotham Knights). In some game disabling steam input is a workaround. |
possibly the same as this issue? #1180 @Pentadrago |
@zany130 |
Fedora 37 kde Wayland, gamescope version 3.11.49
I'm using a dual sense controller
Launch any game with gamescope on, there is no controller input, keyboard/mouse works just fine.
I tried this with big picture on and off, it's a problem for both. (This is the updated deckui big picture.)
I tried this on x11 and it's not an issue there, might have something to do with global shortcuts not implemented on Wayland.
The text was updated successfully, but these errors were encountered: