hrydgard
[CONTROLLERS] no access to dualsense once an app has enabled enhanced features in SDL
Game or games this happens in
NA - PPSSPP interface
What area of the game / PPSSPP
When the SDL hint to enable advanced features for Dualsense is enabled in SDL (the controller will have the white led switched on above the mic), the compatibility with DirectInput is lost, thus rendering the controller unresponsive in PPSSPP. Only solution is to switch the controller off and on again, which will set the controller back to "normal state".
What should happen
The behaviour is normal, as documented in SDL documentation. However, would it be possible to add SDL as input driver for PPSSPP ? Most apps now use SDL as input wrapper, as it offers large controller compatibility and unified button IDs.
It's a huge task but might be worth considering.
Logs
No response
Platform
Windows
Mobile device model or graphics card (GPU)
RTX 3050
PPSSPP version affected
any
Last working version
No response
Graphics backend (3D API)
Vulkan
Checklist
- [x] Test in the latest git build in case it's already fixed.
- [x] Search for other reports of the same issue.
- [ ] Try resetting settings or older versions and include if the issue is related.
- [ ] Try without any cheats and without loading any save states.
- [ ] Include logs or screenshots of issue.
It's a consideration. However, I don't really like relying on SDL since it complicates the build a little (and we've done fine without it so far). I might have to give up on this eventually though.
Anyway I recently went ahead and added native HID input from DualSense through USB for 1.20. It even supports tilt. You can test it in the latest builds from https://www.ppsspp.org/devbuilds/ .
It currently rejects bluetooth connections (since that didn't work on the ARM64 laptop I originally tested it on, due to complicated reasons) but I might consider adding that too.
