-
Notifications
You must be signed in to change notification settings - Fork 22
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
PS4 DS4 triggers and touchpad not working in PS remote play #1
Comments
Hi, thanks :) Triggers work for me on Gamepad Tester: https://gamepad-tester.com Would you have more info so I can reproduce the issue? As for the touchpad, are you using the report directly? I have never tried that, could you share a code snippet please? |
Closed for inactivity / could not reproduce the issue. Please reopen if you encounter this issue. |
The triggers don't work when trying to use the DS4 virtual controller through PS remote play to a PS5 console. They are reported as working on gamepad-tester, and I've read them with both DS4Windows->Xinput, as well as pygame. All report the triggers as working. I have had multiple users try this and all report the same issue: R2/L2 don't work on the PS5 console through remote play. I've not yet found why it won't read the input from vgamepad properly. Additionally, a physical DS4 controller itself will have the triggers work on remote play properly. |
Hmm that sounds like a vigem issue, let's see whether Nefarius knows more about this. |
Apparently Nefarius thinks this should work and that I might have not formatted the DS4 report correctly. If anyone knows what I might have done wrong help would be appreciated, because I don't have PS remote play to test this. |
Seems related: 236563 Apparently it is Sony who added a check to their software to make sure that what is connected in an authentic DS4 controller. |
Hi! Great wrapper. It seems as though the triggers do not work, and neither does the touchpad input.
No errors are thrown, but nothing ends up happening with those.
The text was updated successfully, but these errors were encountered: