Xbox Wireless controllers buttons layout/labels wrong (also ozone pictures)
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
First and foremost consider this:
- Only RetroArch bugs should be filed here. Not core bugs or game bugs
- This is not a forum or a help section, this is strictly developer oriented
Description
In the entire Retroarch everywhere it writes that Xbox Wireless controller has Y left, B down, A right and X top. So all the default actions are effd up and images are wrong in your ozone pictures etc.
Expected behavior
Button labels (A,B,X,Y) and position description (down,left,right,top) in configuration and in images match the physical device.
If it detects you are using Xbox Wireless Controller, then the pictures and text and real controller layout is applied for Xbox Wireless Controllers, not something else.
X = left; Y = top; A = bottom; B = right.
Actual behavior
Actually X and Y are swapped and A and B are swapped.
Also in the configuration for inputs there is written WRONG:
"B button (down)" ---> NO! B is NOT down, but right! (which makes also the picture with 4 dots wrong)
"Y button (left)" ---> NO! Y is NOT left, but top! (which makes also the picture with 4 dots wrong)
"A button (right)" ---> NO! A is NOT right, but down! (which makes also the picture with 4 dots wrong)
"X button (top)" ---> NO! X is NOT top, but left! (which makes also the picture with 4 dots wrong)
So it's like even very confusing to remap anything myself as I have no clue if I should go by the real button labels (A,B,X,Y) or by the directions/images (left,right,top,bottom).
And if the "main theme" there are the directions, not the button labels, then swap the place:
"B button (down)" to "Down (A button xbox)" for Xbox controller and "Down (B button on Snes)" for snes controller. Even having "Down (B button on Snes)" written would make MORE SENSE because then I know to use "down" instead of "B", because I don't use snes controller, but right now it's just absurd.
Steps to reproduce the bug
- just go into input configuration and observe the nonsense.
Bisect Results
no idea what this "bisect" even means.
Version/Commit
You can find this information under Information/System Information
- RetroArch: [1.8.5 I assume (it's not written in the information, system, only git version is there: 8bcd74bf42]
Environment information
- OS: Manjaro Linux
- Compiler: GCC 9.3.0 64-bit
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
The issue names no files or tests; first reproduce the problem in RetroArch's input configuration with an Xbox Wireless controller and inspect the controller-label, layout, and Ozone image handling. Done means the displayed A/B/X/Y labels, directional descriptions, and images match the physical Xbox layout without breaking other controller layouts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100