games not recieving controller input on wayland

[a73s]

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.

[surafel911]

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.

[a73s]

Any additional details? How are you running gamescope? I have a very similar setup so I'd be interested in testing if this is happening.

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.

[SkyLeite]

Same issue here with Monster Hunter World and Sway. Here's the output of gamescope --debug-events --debug-hud -f -e %command% > /home/***/gamescope.log with Monster Hunter World:

gamescope.log

Hardware Information (from Steam)

Computer Information:
    Manufacturer:  Gigabyte Technology Co., Ltd.
    Model:  B450 AORUS M
    Form Factor: Desktop
    No Touch Input Detected

Processor Information:
    CPU Vendor:  AuthenticAMD
    CPU Brand:  AMD Ryzen 9 5900X 12-Core Processor            
    CPU Family:  0x19
    CPU Model:  0x21
    CPU Stepping:  0x2
    CPU Type:  0x0
    Speed:  4950 Mhz
    24 logical processors
    12 physical processors
    HyperThreading:  Supported
    FCMOV:  Supported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Supported
    SSE41:  Supported
    SSE42:  Supported
    AES:  Supported
    AVX:  Supported
    AVX2:  Supported
    AVX512F:  Unsupported
    AVX512PF:  Unsupported
    AVX512ER:  Unsupported
    AVX512CD:  Unsupported
    AVX512VNNI:  Unsupported
    SHA:  Supported
    CMPXCHG16B:  Supported
    LAHF/SAHF:  Supported
    PrefetchW:  Unsupported

Operating System Version:
    "NixOS 23.05 (Stoat)" (64 bit)
    Kernel Name:  Linux
    Kernel Version:  6.2.0-rc6
    X Server Vendor:  The X.Org Foundation
    X Server Release:  12201008
    X Window Manager:  wlroots wm
    Steam Runtime Version:  steam-runtime_0.20230118.0

Video Card:
    Driver:  AMD AMD Radeon Graphics (gfx1100, LLVM 15.0.7, DRM 3.49, 6.2.0-rc6)
    Driver Version:  4.6 (Compatibility Profile) Mesa 23.1.0-devel
    OpenGL Version: 4.6
    Desktop Color Depth: 24 bits per pixel
    Monitor Refresh Rate: 239 Hz
    VendorID:  0x1002
    DeviceID:  0x744c
    Revision Not Detected
    Number of Monitors:  3
    Number of Logical Video Cards:  1
    Primary Display Resolution:  5120 x 1440
    Desktop Resolution: 5120 x 2520
    Primary Display Size: 46.85" x 13.39" (48.70" diag)
                                            119.0cm x 34.0cm (123.7cm diag)
    Primary VRAM: 24576 MB

Sound card:
    Audio device: ATI R6xx HDMI

Memory:
    RAM:  48102 MB

VR Hardware:
    VR Headset: None detected

Miscellaneous:
    UI Language:  English
    LANG:  en_US.UTF-8
    Total Hard Disk Space Available:  929807 MB
    Largest Free Hard Disk Block:  136660 MB

Storage:
    Number of SSDs: 3
    SSD sizes: 2000G,1000G,1000G
    Number of HDDs: 0

Edit: As said in #822, running Steam itself through gamescope rather than a game itself makes controller input work.

[bloodwolfepc]

still have this issue also.

[BrknRobot]

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.

[BrknRobot]

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

[danielw01]

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

[JoshElias]

I'm having this issue also on wayland. I built gamescope myself so I'm on the latest version.

[Pentadrago]

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.

[zany130]

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? https://github.com/ValveSoftware/gamescope/issues/1180 @Pentadrago

[Pentadrago]

@zany130 Thank you, that seems to be the issue in my case as steam input stopped working in the last few weeks.