ValveSoftware / ValveSoftware/Proton
Controller Input gets mapped incorrectly or stop working all together seemingly randomly
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 32.8k
- Forks
- 1.6k
- PR merge metrics
- PR metrics pending
Description
I just had an issue where Soul Caliber XI had the mappings of all my Xbox controllers incorrect and in some games the controller wasn't detected whatsoever. Simply deleting the game prefixes having the issues to generate a fresh one resolves the issues. I'm not entirely sure what causes this yet.
This isn't the first time I've had to do something like this so I'm assuming it's a bug that is probably going to he hard to isolate.
Proton 6.3.8 and Experimental
Pop OS 21.04
It effects all controllers including PS3/PS4 gamepads.
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
No files, tests, or code entry points are identified. Start by reproducing the controller-mapping and detection failures with the reported Proton versions, Pop!_OS, and affected gamepads. Done would require isolating the cause and confirming that mappings and detection remain correct without deleting game prefixes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100