tvOS Controller Profile Button Mapping Issue
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
When using controller profiles at the tvOS level to remap buttons, both the remapped button and the unmapped button are triggered simultaneously. This issue occurs with the Switch Pro controller.
Expected behavior
- A button should function as 'back'.
- B button should function as 'select'.
Actual behavior
- Pressing the A button triggers 'select' followed by 'back'.
- Pressing the B button triggers 'back' followed by 'select'.
Steps to reproduce the bug
- Use a Switch Pro controller with the default settings:
- A button: 'select'
- B button: 'back'
- Attempt to remap buttons in RetroArch Retropad (has no effect).
- Remap buttons in tvOS controller profile settings (A->B and B->A).
- Observe that pressing the A button now triggers 'select' followed by 'back'.
- Observe that pressing the B button now triggers 'back' followed by 'select'.
Bisect Results
[Try to bisect and tell us when this started happening]
Version/Commit
You can find this information under Information/System Information
- RetroArch: [version/commit]
Environment information
- OS: tvOS
- Compiler: [In case you are running local builds]
Contributor guide
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 issue with a Switch Pro controller on tvOS, using the tvOS controller profile settings and RetroArch Retropad mappings described here. Check the reported A/B event order and gather the RetroArch version or commit from Information/System Information. Done means remapping A to B and B to A produces only the intended action for each button.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100