Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
About DualShock 3 triggers in one of mappings
See original GitHub issueHey,
while I realize this database is not supposed to overwrite stock SDL mappings, there is at least one which is plain wrong.
I’m talking about one of DS3 mappings, namely the one with GUID 050000004c0500006802000000800000. In SDL (and thus in this database too) its triggers are defined as:
lefttrigger:b6,righttrigger:b7
however, mapping this specific controller in Steam Link app gives a better mapping, where triggers are axes:
lefttrigger:a2,righttrigger:a5
What should be done about this? Other DualShock 3 mappings have correctly mapped triggers, this one is an outlier and my pad just happens to use that mapping on Raspbian.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I have now submitted a patch for this mapping: https://bugzilla.libsdl.org/show_bug.cgi?id=4504
Fingers crossed it gets answered in a timely manner!
Great! Once SDL 2.0.10 releases, I’ll update our SDL mappings and the fix will roll in. Thx for going through the process 😃