Incorrect Autoconfiguration of Xbox 360 / One controller

Okay. I have two machines. One with a BARE NAKED INSTALLATION with everything deleted and reinstalled with one rom loaded in.

On BOTH of them I encounter the following situation, when using an Xbox360 wireless controller, and an 8bitdo sn30 which registers as an X Box One controller when in (xinput) mode

Code:

Xbox 360 wired controller

Retroarch n64 launch mupen64plus-next 2.2 vulkan
L3 trigger +4

Right analog y -4 +4
Right Analog X -3 +3

This causes three things
1. Y axis on the right stick has "X" input
2. the X axis on the right stick does nothing
3. L2 does L2 and one side of RX axis.

If I manually, in any Retroarch situation, go to the MAIN SETTINGS, and remap the control. The correct setting through the mapping is

Code:

L2 trigger +4
Right analog  y -3 +3
Right Analog X -2 +2

And it works properly. This does not maintain however.

If I;
disable ALL autoconfigure from ES then there is no autoconfigure and that kind of defies the whole point.

If I;
disable autoconfig ONLY on [Affected system, primarily N64] (through the select menu);
Make changes in MAIN MENU of RA;
Save CONFIG...

Then it will work UNTIL I load any piece using RA with an autoconfig... then the problem returns next run of [Affected system, primarily N64]

It does not matter what core is loaded or even naked RA. L3 is set to +4 and right stick X is set to -+4 and Y +-3.

I went investigating around the 'autoconfig' files that I could find in ES and RA and found the following

Code:


Ra/autoconfig/dinput (RA indicates the input driver is DINPUT when running from RB, Xinput is not an option)
input_l2_axis = "+2"
input_r_x_plus_axis = "+3"
input_r_x_minus_axis = "-3"
input_r_y_plus_axis = "+4"
input_r_y_minus_axis = "-4"

ra/autoconfig/sdl2 (RA Inidcates CONTROLLER driver is sdl2 when running from RB)
input_l2_axis = "+4"
input_r_x_plus_axis = "+2"
input_r_x_minus_axis = "-2"
input_r_y_plus_axis = "+3"
input_r_y_minus_axis = "-3"

Retroarch/autoconfig/xinput
Xbox 360 Wired Controller (smilar/same for Xbox One)
input_l2_axis = "+4"
input_r_x_plus_axis = "+2"
input_r_x_minus_axis = "-2"
input_r_y_plus_axis = "-3"
input_r_y_minus_axis = "+3"

retroarch/autoconfig/x
input_l2_axis = "+2"
input_r_x_plus_axis = "+3"
input_r_x_minus_axis = "-3"
input_r_y_plus_axis = "+4"
input_r_y_minus_axis = "-4"

emulationstation es_input.cfg (360 wired section)
<input name="l2" type="axis" id="2" value="1" />
<input name="joystick2left" type="axis" id="3" value="-1" />
<input name="joystick2up" type="axis" id="4" value="-1" />


retroarch.cfg
input_player1_l2_axis = "+4"
input_player1_r_x_minus_axis = "-3"
input_player1_r_x_minus_btn = "nul"
input_player1_r_x_minus_mbtn = "nul"
input_player1_r_x_plus = "nul"
input_player1_r_x_plus_axis = "+3"
input_player1_r_x_plus_btn = "nul"
input_player1_r_x_plus_mbtn = "nul"
input_player1_r_y_minus = "nul"
input_player1_r_y_minus_axis = "-4"
input_player1_r_y_minus_btn = "nul"
input_player1_r_y_minus_mbtn = "nul"
input_player1_r_y_plus = "nul"
input_player1_r_y_plus_axis = "+4"


When mapping the controller in ES it records L2 as +2 and the Right Stick as 3 and 4.

It seems like somewhere in the process of autoconfiguring that the right analog stick is getting set to the wrong axis from what RA at least thinks it should be? Theoretically any of those configurations should not replicate the problem if correctly loaded, in no autoconfig that I find do I see L3 and Right Stick input being the same.

Unhelpful Answers
[13] How do I create a specific controller configuration in Retroarch ?
This only allows the changing of target-system button mappings based on what RA globally thinks the controller is... +4 is still in two locations, so if you put anything on what RA says is Right Stick (+-4) then L2 will still trigger that action. And despite the available options, one axis of the right stick is perpetually unavailable in this case.

[9] How and why to deactivate the automatic configuration of controllers ?
When I last tried to discuss this problem I was admonished for not using the autoconfig, after all if it is an xbox360 controller that works perfectly (or 8bitdo which reads as Xbox One, which I since discovered its a config issue and not a controller issue) then it should work as expected.

Seemingly repeat issue
This seems to be a configuration issue with the same symptoms repeated here:
https://retrobat.forumgaming.fr/t398-probleme-manette-xbox-one-jeux-n64?highlight=Xbox where the fellow settled for using the C-Buttons Mode

Also here https://retrobat.forumgaming.fr/t675-mupen-64-plus-next-core-runs-laggy-and-controls-are-wrong-mapped

Previously with me here https://retrobat.forumgaming.fr/t612-crash-on-hotkeysave-state-missing-scraped-data#3635

same problem here, https://retrobat.forumgaming.fr/t342-controller-issue-affects-at-least-8bitdo-sn30-pro-in-windows-mode-x-input with an implied fix

Edit es_input.cfg and replace
CODE:
<input name="joystick2left" type="axis" id="3" value="-1" />
<input name="joystick2up" type="axis" id="4" value="-1" />

with
CODE:
<input name="joystick2left" type="axis" id="2" value="-1" />
<input name="joystick2up" type="axis" id="3" value="-1" />

HOWEVER, this seems to break auto configured right stick behavior in other non RA emulators (Dolphin native is the one I tested)

As a bonus, I just freshly attached a Nintendo Pro Controller and did the config with ES, the controller mapped perfectly as expected into RA without a doubling of L2 and with the right analog stick working as expected, that controller has some other bug though, since I've never used it on windows before that is what I blame for now.

I'm fairly certain this is a known issue with the current build of Retrobat. I've seen it mentioned that it will be fixed in the next update. For now, you will have to turn off autoconfig in all affected sections of Retrobat (or entirely in developer settings), then manually map your right analog controls in Retroarch, and save the current config. It's not a major deal, a small mistake in Retrobat, and can be fixed.