-
Notifications
You must be signed in to change notification settings - Fork 39
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
Added support for PS5USB controllers #12
base: master
Are you sure you want to change the base?
Conversation
Added initial support for PS5 controllers by creating a combination of the PS4 controller class and Ludwig Füchsl's DualSense Windows driver https://github.com/Ohjurot/DualSense-Windows
@josephduchesne Nice to see that! From my side the comments with the attribution and license in the source code is totally fine for this project. |
uint8_t battery : 4; | ||
uint8_t dummy3 : 1; | ||
uint8_t battery_full : 1; | ||
uint8_t dummy4 : 2; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not think this is correct. These are all 0's on my controller except for the 1st bit, which seems to be used for the microphone. I do not know about the battery_full
bit though, as I'm not sure if my controller is fully charged or not.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@josephduchesne what is your take on this?
Added initial support for PS5 controllers by creating a combination of the PS4 controller class and Ludwig Füchsl's DualSense Windows driver https://github.com/Ohjurot/DualSense-Windows
This supports all of the feature's that @Ohjurot supported in his driver, including 3 different haptic modes.
Since the force feedback in the triggers is pretty complicated, I used the DualSense Windows functions and datastructures with minimual modification, which is why the PS5Trigger.h and PS5Trigger.cpp files retain their source license and copyright (MIT license). I don't believe that this is a problem given that the explicitly copied code sections are all properly licensed and attributed as far as I can tell.
I have only included the USB class, however it should be relatively straight forward to create a Bluetooth version. I just don't have a great hardware setup for that, and my use case prefers USB.