I have what is probably a simple question. I am running the Android version of RetroArch, and it is auto-detecting my PS3 controller perfectly.
However, I would like to swap some of the buttons on a couple of cores (SNES, etc.). However, when I enter the button mapping screen, I am unable to change the button mapping, it just displays, “unknown”.
Is there a way to customize the PS3 mappings per core? Is there an alternate configuration file I can use?
Thanks a lot!
JTip
You can manually bind buttons by disabling autoconfig in the input options. The manual options that were greyed out will be then be accessible.
There has been quite a few requests for this functionality on Android but apparently it’s quite a task to implement.
I actually found the Dualshock 3 buttons to be mapped completely wrong in all cores (as in, the Sixaxis Controller software borked them). I went into Street Fighter 2 on a Playstation 1 core, went into the button config (for button mapping test) and realized they didn’t correspond correctly. I actually remapped the buttons in the sixaxis controller software. Turned out I had to change the mappings in the sixaxis gamepad to the following (after which, when using SF2 to test again, the buttons properly corresponded).
In Sixaxis Gamepad Mappings: Cross=X Circle=Y Square=A Triangle=B
So now that the buttons are mapped CORRECTLY, they actually also correspond correctly to that of SNES (another 4 thumb button controller).
The first thing I will do if custom mapping per core gets implemented is fix the mapping for all 2 button cores (NES, GB etc…) because as it stands the CORRECT way is backwards from how anyone would use them. It should be Square=B and Cross=A (using a Dualshock 3 controller in a NES or GB game).
I’m aware of the change nintendo did from their 2 button layout (NES, GB) to their 4 button (SNES) layout where they put the B and A buttons as the bottom and right. They realized that when playing classic “Mario” style games that people would have to hold their hand in an awkward position to have the run and jump (B and A respectively on the SNES) work the same. Which is why they allowed you to select controller layout that made Y=Run and B=Jump (SNES controller), which everyone used.
But I’ve brought this up before and it didn’t gain any traction so I’ll just be patient. There are many more important issues for the devs to resolve than this. 
In my opinion this is incorrect I believe the correct way is the way which most closely matches the physical original, not what someone thinks feels better… The physical layout of a GBA or GB/GBC most closely corresponds to using Cross=B and Circle =A. I suppose NES would be more personal opinion since the original NES has perfectly even A and B buttons. But on a GBA and GB/GBC the A button is to the right and above the B button and I would prefer to use a controller that most closely matches that.
This is why personal customization would be nice though. Not everyone feels the same.
[quote=“Shifted”]
In my opinion this is incorrect I believe the correct way is the way which most closely matches the physical original, not what someone thinks feels better… The physical layout of a GBA or GB/GBC most closely corresponds to using Cross=B and Circle =A. I suppose NES would be more personal opinion since the original NES has perfectly even A and B buttons. But on a GBA and GB/GBC the A button is to the right and above the B button and I would prefer to use a controller that most closely matches that.
This is why personal customization would be nice though. Not everyone feels the same.[/quote]
Yeah, I can definitely see how you are associating the button layout of GB and GBA with X and O on the Dualshock controller in that they are angled. However, you’ll notice that the angle of these buttons are at a much higher degree on the Dualshock than that of a GB and GBA. Which is exactly why when Nintendo moved to the 4 button layout on the SNES (matches the layout of the Dualshock) for their flagship Mario titles, they made the Y button = old B and B button = old A in game by default. This allowed for a natural wrist/hand angle when playing games in the style where people usually hold down the dash/run button with the tip of their thumb and then pressed the jump button with their thumb joint.
Additionally, when you play Super Mario Allstars on the SNES that includes the original NES titles like Super Mario Brothers, the Y button is dash and the B button is jump. So in reality, if the button layout was to be as accurate as possible with respect to what Nintendo wanted, my suggestion would actually be (more?) correct, no?
What we can all agree on is that per core button configuration will definitely be nice. I’m sure when Squarepusher and his crew get Retroarch functioning the way they like, they’ll start adding less important yet highly requested/sought after functionality such as this. Patience is a virtue!
~Cheers
There is type A and B in SMAS to change the behavior as well. Nintendo might be crazy, but they know how to get controls right, at least on the early Mario(s).