mirror of
https://github.com/games-on-whales/wolf.git
synced 2026-10-15 21:12:08 +00:00
[GH-ISSUE #187] PS5 Controller mapped wrong #124
Labels
No labels
🧠 1 - 🤖 999
AMD
bug
bug
cannot reproduce
documentation
duplicate
easy
enhancement
enhancement
enhancement
fixed?
fixed?
good first issue
hard
help wanted
Intel
invalid
LXC
medium
moonlight-protocol
Multi GPU
nixos
not a bug
nvidia
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
games-on-whales/wolf#124
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @danny9484 on GitHub (Mar 23, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/187
Hello, when using a Playstation 5 Controller I noticed that the buttons aren't mapped properly. Same seems to be happening with a PS4 Controller, I have one here in case you want me to test every button of that one too.
I have tested this inside steam with the moonlight-qt flatpak linux and moonlight-ios client. My Host is Fedora 42 Server with the wolf container running on podman. I tested the stable and alpha tag.
Here is a list of Buttons that seem to be mapped wrong. First is the Button that I pressed on the controller and second is what Steam registered.
Ps button - L3
L3 - R3
R3 - Ps button
left trigger - right thumb horizontal
right trigger - right thumb vertical
right thumb horizontal - left trigger
right thumb vertical - right trigger
cross - square
square - triangle
triangle - circle
circle - cross
@ABeltramo commented on GitHub (Mar 23, 2025):
Can you share the full logs from Wolf using
?
I'm trying to see if you are actually able to create a dualsense joypad on the server or if it's falling back to an xbox joypad.
@danny9484 commented on GitHub (Mar 23, 2025):
looks like it does, Steam also sees it as a PS5 Controller.
@ABeltramo commented on GitHub (Mar 23, 2025):
Ok, thanks for checking. Is this happening only with the ios Moonlight client? Which version are you using?
@danny9484 commented on GitHub (Mar 23, 2025):
it happens on the ios Moonlight client (9.0.2) and the Linux Client from Flatpak (6.1.0).
@ABeltramo commented on GitHub (Mar 24, 2025):
On a second look at your logs I've noticed:
could it be that you haven't added the mount point
/dev/:/dev/:rwin Wolf as specified in the quickstart guide?@danny9484 commented on GitHub (Mar 24, 2025):
I had mounted /dev/input. when mounting /dev the warning does go away but it didn't fix the issue with the dualsense.
I also tried to use the exact command from the getting started page, just changing to podman ofc, still same issue.
@kode54 commented on GitHub (Mar 25, 2025):
I found this was related to the host kernel having an old hid playstation driver. Apparently they changed the button mappings at some point?
Edit: What. A beta OS? Did they break hid playstation in kernel 6.14?
@ABeltramo commented on GitHub (Mar 26, 2025):
I can't replicate this issue on my end and I fell that @kode54 might be right, which kernel version are you running? I'm on
6.13.8on Arch and everything seems to work correctly on my end.I've also updated
inputtinoto the latest and brought a few tweaks and fixes specifically for the DualSense on https://github.com/games-on-whales/wolf/pull/189 you can try that image out by running(currently building...)
@danny9484 commented on GitHub (Mar 26, 2025):
dev-dualsense didn't fix my issue.
I will probably only find time on the weekend to test with Fedora 41 on kernel 6.13. Right now my machine is running kernel 6.14.0 RC7
fyi @ABeltramo dev-dualsense did fix vibration and there seems to be some LED color management to be working. On iOS the default LED color is orange, when I connect with moonlight the LED now changes to blue which is the usual default color of the controller. But in steam I'm unable to find a option to customize the color.
@ABeltramo commented on GitHub (Mar 26, 2025):
I'll check if 6.14 broke something once it gets available in Arch, I don't see any specific commit for
hid-playstationthough..It should be under
Calibration & Advanced settingsYou should have the following
If you don't, can you check if inside the Steam container (not Wolf) you get
/dev/hidraw**mounted? And what are the permissions for it?@zexi commented on GitHub (Mar 28, 2025):
I've tested this on debian 12 with 6.12 kernel and archlinux with 6.13.
It's ok with archlinux but wrong mapping with debian.
The controller name showing in steam is 'PS5 Controller' of debian and 'DualSense Wireless Controller' of archlinux.
What differences I see from dmesg are hid-generic module using of archlinux.
@ABeltramo commented on GitHub (Mar 28, 2025):
Thanks for reporting @zexi
Do you consistently get the same mapping mismatch that has been originally reported in this issue when running it in Debian?
@Grarak commented on GitHub (Mar 28, 2025):
Have the same problem with ubuntu 24.10 running 6.11.0-21 kernel
With the same consistant mapping mismatch
Ran this in the steam container
@danny9484 commented on GitHub (Mar 29, 2025):
I didn't yet revert to fedora 41 but did some more testing. Inside the wolf container I can see the following hidraw devices
hidraw8 is the controller, I can also read it with cat for example. I have tried the same with the steam container
but cat fails on hidraw8 in the steam container
I have also tested the virtual device inside the steam controller with evtest where for example the cross button reports BTN_SOUTH which sounds correct to me.
just as @zexi mentioned my controller is also recognized as PS5 Controller by steam, but I also see the hid-generic line in my dmesg
@ABeltramo commented on GitHub (Apr 1, 2025):
@danny9484 @Grarak @zexi thanks all for reporting, after booting up a clean Debian installation I was finally able to reproduce the issue. I've just pushed a potential fix, could you guys try out
and let me know if that fixes it for you too?
@Grarak commented on GitHub (Apr 1, 2025):
Yes works now! Thanks for the quick fix
@danny9484 commented on GitHub (Apr 1, 2025):
yes I can also confirm that it works now. LED controls work inside steam too
thank you very much :D