[GH-ISSUE #403] No joypad input in game - but Steam overlay works with joypad #266

New issue

Closed

opened 2026-10-15 12:59:02 +00:00 by bsakaguchi · 4 comments

bsakaguchi commented

2026-10-15 12:59:02 +00:00

Owner

Originally created by @Vantage-DS on GitHub (Apr 29, 2026).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/403

Host: Pop!_OS 24.04 LTS

I've got a really strange problem that I can't figure out.
I'm using a PS5 (dualsense) joypad and i've also tried with a PS4 dualshock. Both plugged in and via bluetooth.

Open Moonlight - the joypad works.
Connect to Wolf - joypad works
Open Steam - joypad works
Navigate through Steam with joypad - all good.
Start a game and try navigate in menus - joypad doesn't work.
Press PS button to open steam overlay - joypad works.

Basically the game itself doesn't recognise the joypad, but everything else is fine.

I've tried enabling/disabling steam input.
Tried disabling steam overlay.
Changed controller groups to root:

 # Allow Wolf access /dev/uinput
KERNEL=="uinput", SUBSYSTEM=="misc", MODE="0660", GROUP="input", OPTIONS+="static_node=uinput", TAG+="uaccess"

# Allow Wolf access /dev/uhid (needed by PS5/DualSense simulation)
KERNEL=="uhid", GROUP="input", MODE="0660", TAG+="uaccess"

# Virtual gamepad setup, which key part is `ENV{ID_SEAT}="seat9"`
KERNEL=="hidraw*",   ATTRS{name}=="Wolf PS5 (virtual) pad", GROUP="root", MODE="0660", ENV{ID_SEAT}="seat9"
SUBSYSTEMS=="input", ATTRS{name}=="Wolf X-Box One (virtual) pad", GROUP="root", MODE="0660", ENV{ID_SEAT}="seat9"
SUBSYSTEMS=="input", ATTRS{name}=="Wolf PS5 (virtual) pad", GROUP="root", MODE="0660", ENV{ID_SEAT}="seat9"
SUBSYSTEMS=="input", ATTRS{name}=="Wolf gamepad (virtual) motion sensors", GROUP="root", MODE="0660", ENV{ID_SEAT}="seat9"
SUBSYSTEMS=="input", ATTRS{name}=="Wolf Nintendo (virtual) pad", GROUP="root", MODE="0660", ENV{ID_SEAT}="seat9"

Other than changing the above and trying that, everything else is default as per setup guide.

I cannot find other people with this problem so I've no idea why it's happening.

Any suggestions?

Thanks

Originally created by @Vantage-DS on GitHub (Apr 29, 2026). Original GitHub issue: https://github.com/games-on-whales/wolf/issues/403 Host: Pop!_OS 24.04 LTS I've got a really strange problem that I can't figure out. I'm using a PS5 (dualsense) joypad and i've also tried with a PS4 dualshock. Both plugged in and via bluetooth. 1) Open Moonlight - the joypad works. 2) Connect to Wolf - joypad works 3) Open Steam - joypad works 4) Navigate through Steam with joypad - all good. 5) Start a game and try navigate in menus - joypad doesn't work. 6) Press PS button to open steam overlay - joypad works. Basically the game itself doesn't recognise the joypad, but everything else is fine. I've tried enabling/disabling steam input. Tried disabling steam overlay. Changed controller groups to root: ``` # Allow Wolf access /dev/uinput KERNEL=="uinput", SUBSYSTEM=="misc", MODE="0660", GROUP="input", OPTIONS+="static_node=uinput", TAG+="uaccess" # Allow Wolf access /dev/uhid (needed by PS5/DualSense simulation) KERNEL=="uhid", GROUP="input", MODE="0660", TAG+="uaccess" # Virtual gamepad setup, which key part is `ENV{ID_SEAT}="seat9"` KERNEL=="hidraw*", ATTRS{name}=="Wolf PS5 (virtual) pad", GROUP="root", MODE="0660", ENV{ID_SEAT}="seat9" SUBSYSTEMS=="input", ATTRS{name}=="Wolf X-Box One (virtual) pad", GROUP="root", MODE="0660", ENV{ID_SEAT}="seat9" SUBSYSTEMS=="input", ATTRS{name}=="Wolf PS5 (virtual) pad", GROUP="root", MODE="0660", ENV{ID_SEAT}="seat9" SUBSYSTEMS=="input", ATTRS{name}=="Wolf gamepad (virtual) motion sensors", GROUP="root", MODE="0660", ENV{ID_SEAT}="seat9" SUBSYSTEMS=="input", ATTRS{name}=="Wolf Nintendo (virtual) pad", GROUP="root", MODE="0660", ENV{ID_SEAT}="seat9" ``` Other than changing the above and trying that, everything else is default as per setup guide. I cannot find other people with this problem so I've no idea why it's happening. Any suggestions? Thanks

bsakaguchi

2026-10-15 12:59:02 +00:00

closed this issue
added the
duplicate

not a bug
labels

bsakaguchi commented

2026-10-15 12:59:03 +00:00

Author

Owner

@ABeltramo commented on GitHub (Apr 29, 2026):

If in wolf-ui/steam you can use the joypad then Wolf is correctly configured; anything beyond that is downstream app/game issues. Steam input needs to be disabled, this is a known issue ( #81 ) then you need a game that natively supports DualSense joypads (aka it doesn't require steam input).
Which specific game were you trying to play?

@ABeltramo commented on GitHub (Apr 29, 2026): If in wolf-ui/steam you can use the joypad then Wolf is correctly configured; anything beyond that is downstream app/game issues. Steam input needs to be disabled, this is a known issue ( #81 ) then you need a game that natively supports DualSense joypads (aka it doesn't require steam input). Which specific game were you trying to play?

bsakaguchi commented

2026-10-15 12:59:03 +00:00

Author

Owner

@Vantage-DS commented on GitHub (Apr 29, 2026):

Thanks for the quick reply!

Ok that makes sense then - I've only tried Grounded and Astroneer so far so I'll look to try a game that specifically supports dualsense.

I'm not concerned about isolation, so will the quick fix you mention in #81 potentially work with steam input?

@Vantage-DS commented on GitHub (Apr 29, 2026): Thanks for the quick reply! Ok that makes sense then - I've only tried Grounded and Astroneer so far so I'll look to try a game that specifically supports dualsense. I'm not concerned about isolation, so will the quick fix you mention in #81 potentially work with steam input?

bsakaguchi commented

2026-10-15 12:59:03 +00:00

Author

Owner

@Steewen19 commented on GitHub (Apr 29, 2026):

The quick fix should work

@Steewen19 commented on GitHub (Apr 29, 2026): The quick fix should work

bsakaguchi commented

2026-10-15 12:59:03 +00:00

Author

Owner

@Vantage-DS commented on GitHub (Apr 29, 2026):