-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Dualsense 5 only partially working (pre-release v2024.1218.135629) #3468
Comments
To clarify which AUR package are you using? Do you have the same issue if you use https://github.com/LizardByte/pacman-repo (beta)? |
I was using this one: https://aur.archlinux.org/packages/sunshine-beta-bin. I didn't know about the official one. Now I have installed the one you linked (and uninstalled the previous one). The problem persist with this package too. Btw since I have opened the online tester again I have gathered some additional info: most of the buttons are correctly recognized. Those that behave incorrectly are: Triggers (L2/R2) - Right Stick.: these two are inverted: the triggers are recognized as the X and Y axis for the Right Stick and the Right Stick X and Y movement are recognized as L2/R2. To be more precise: L2 <--> Xaxis and R2<-->Yaxis. XOTriangleSquare: these are rotated by one position. Example: if I press Square it is recognized as X. Can't say anything about the buttons: L3, R3 and playstation logo. The keypress signal is there but I don't know if they are correctly recognized (no visual feedback). Mousepad and microphone have no feedback at all in the tester on the tester but the mousepad is working without problems in the OS. |
Sorry for the multiple posts. I am doing some other tests and I have found this site: https://ds.daidr.me/ (it has a git here: https://github.com/daidr/dualsense-tester) Currently we have: |
Thanks for all the info, I'm afraid I'll need some more 😅 To give you a bit more context, the Desktop environment (KDE) doesn't deal with joypads because compositors in Linux (X11/Wayland) don't recognise them. So, what every app/game does is to access the gamepads as USB devices directly via There are a few high-level libraries to do that, and the most common is SDL, which is used by Steam, Moonlight, and Proton for example. Steam famously packages its own libraries instead of using the system provided ones, so it makes sense that you see different results compared to other apps like the web browser. To make things more complicated, some apps access a lower-level API when dealing with DualSense in order to properly support gyro, acceleration, and force feedback (which is why gamepad tester behave differently than the other website which uses To try and narrow this down a little it would be very helpful if you could provide the followings:
|
I have solved some of the issues, and those were my fault. gamepad tester: working Now gamepad tester recognize all the inputs. KDE: still strange behavior This behavior is reproduced also when sunshine is running on my laptop. testing on games sdl2-jstest
|
Thanks for the detailed report! If The only other thing I could think of is that there are some things that we don't support like the microphone (Moonlight doesn't support it) and Haptic Feedback (I've never bothered implementing it since so few titles supports it). I think both those games should have full DualSense support, so I wonder if the game fails to pick up the pad because we miss something specific that they require from a (virtual) PS5 joypad.. Do you have any other non-Steam and non ex PS exclusive game to test? 😅 |
Also,
can you check permissions on the created |
Horizon Forbidden West: In general nothing happens like if no input is received at all by the game, but if I smash all the buttons randomly sometimes something happens, but it does not seems to be linked to specific buttons. I checked a lot of game on my library yesterday, unluckly my non-steam game catalogue has few games that are made with a gamepad in mind. Also those that have a gamepad in mind tends to be old and may not have support for ds5. Those were the two I found that had working support when directly connected. Witcher 2 recognized the input as an Xbox controller but I didn't test it throught sunshine. I will be out for the holidays, but if you think it is worth it I can do some more tests on my return. |
That is tied to Sunshine's installed udev rules, what permissions do you have for the joypad when plugged in the host? Are you part of the As for the two games, could you share a bit more info on how are you installing and running them? Is it via Heroic/Lutris? Which Proton version are you using?
No worries, enjoy your holidays!! |
Is there an existing issue for this?
Is your issue described in the documentation?
Is your issue present in the latest beta/pre-release?
This issue is present in the latest pre-release
Describe the Bug
Without STEAM (steam was closed and not running in background)
With dualsense5 plugged in the client (and recognized by sunshine in the logs).
option 1) go to: https://hardwaretester.com/gamepad. The vendor and the product written are correct, but the button pressed on the gamepad do not correspond to those received by the tester. For example: the triggers are recognized as x axis and y axis of the right stick.
option 2) go to the settings of KDE, gamepad section. There you can see the input pressed on the pad. There is not a visual help in this case, but the behavior is different then when the controller is directly plugged into the "server".
In summary: if I open heroic or a game the gamepad does not behave as expected.
Inside STEAM
In steam: if i open steam and go to the controller section, the gamepad is correctly recognized. If I use the tester inside steam the input are correctly recognized (even the gyro when trying the calibration). If I play a game in steam the gamepad works as inteded.
If i use the desktop override offered by steam in the background the issues outside of steam continue to be present.
Final result: steam recognize the gamepad correctly, but KDE and other apps don't.
Expected Behavior
The correct inputs should be recognized in KDE too, not just steam.
Additional Context
Tested from two different clients: moonlight on my laptop and moonlight on my LG TV.
I don't know if this is problem of ManjaroKDE or sunshine. In theory manjaro kde is perfectly able to recognize the ds5 (it is recognized when direclty plugged in).
My guess is that the approach used to pass the inputs from client to server is not digested by KDE.
Host Operating System
Linux
Operating System Version
Manjaro - KDE v6.2.4 - Kernel v6.6.65
Architecture
amd64/x86_64
Sunshine commit or version
v2024.1218.135629
Package
Linux - AUR (Third Party)
GPU Type
NVIDIA
GPU Model
3070Ti
GPU Driver/Mesa Version
550.135
Capture Method
NvFBC (Linux)
Config
Apps
Relevant log output
The text was updated successfully, but these errors were encountered: