ValveSoftware / ValveSoftware/Proton
dualsense controllers don't work correctly at all
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 32.8k
- Forks
- 1.6k
- PR merge metrics
- PR metrics pending
Description
this bug affects ALL proton versions, including custom ones
in upstream wine, wine has been "patched" (happened unintentionally lmao) to work with the dualsense controller and it works well. Unfortunately, proton has not received the same treatment, and in fact, it is even worse than stock wine. (causing me to prefer stock wine for playing games!!!)
issues with the dualsense controller: (all games)
- no vibration (over bluetooth)
- no inputs in some games (over bluetooth)
- no plug and play (all games, but happens sometimes)
- incorrect controller glyphs after unplugging and plugging back in (sometimes)
- probably numerous other issues
otherwise the controller works fine
games tested: rocket league, riverbond and verdun
note: not running through steam
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the DualSense behavior over Bluetooth and wired connections in Rocket League, Riverbond, and Verdun, then compare it with upstream Wine as described. Done means the reported vibration, input, plug-and-play, and controller-glyph problems are resolved across Proton versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- game-dev, tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100