Hi @w0nderw0rm , did @mitu ‘s solution allowed you to use just the Xbox One controller, or the solution also allows you to use the Nimbus Steelseries?

I just started researching which controller to order that would work best for RetroPie AND Apple Arcade on iPhone, and it looks like the Steelseries Nimbus+ is a great controller (but I’m not sure it works with RetroPie).

Is there a better controller I should consider?
Maybe the 8bitdo SN30 Pro+ ?

So I just wiped InputAutoConfig.ini and started again.

When it's this:

; Keyboard_START [Keyboard] plugged = True plugin = 2 mouse = False DPad R = key(100) DPad L = key(97) DPad D = key(115) DPad U = key(119) Start = key(13) Z Trig = key(122) B Button = key(306) A Button = key(304) C Button R = key(108) C Button L = key(106) C Button D = key(107) C Button U = key(105) R Trig = key(99) L Trig = key(120) Mempak switch = key(44) Rumblepak switch = key(46) X Axis = key(276,275) Y Axis = key(273,274) ; Keyboard_END

the game works perfectly, but keyboard only - WASD and cursors and a few others.

When I add this:

; usb gamepad _START [usb gamepad ] plugged = True Start = button(6) A Button = button(1) B Button = button(2) X Axis = "hat(0 Left Right)" Y Axis = "hat(0 Up Down)" ; usb gamepad _END

the keyboard stops working and the Start, A and B buttons all map to the proper buttons on the arcade joystick, (and button 5 quits back to EmulationStation) but the stick itself does absolutely nothing.

Those X and Y axis lines are taken from some semi-gibberish here:

https://retropie.org.uk/docs/Nintendo-64/

where it says *"Note for configuring Arcade Joystick or non analogue controller to use N64 correctly.
Changing the below inside /opt/retropie/configs/n64/InputAutoCfg.ini

From X Axis = "hat(0 Left, 0 Right)" Y Axis = "hat(0 Up, 0 Down)"

To X Axis = "hat(0 Left Right)" Y Axis = "hat(0 Up Down)""*

But none of those lines, with or without quote marks, make the joystick do anything at all.

If I change it to:

; usb gamepad _START [usb gamepad ] plugged = True Start = button(6) A Button = button(1) B Button = button(2) DPad D = hat(0 Down) DPad U = hat(0 Up) DPad L = hat(0 Left) DPad R = hat(0 Right) ; usb gamepad _END

nothing changes. The stick still does nothing, whether I put quotes round the hat commands or not.

What in blazes do I need to do to make the dumb emulator recognise the stick?

@mitu This was it! I have a script that controls an LED light/Power button on my case, (as well as shows heat/fan speed, etc) and it seems that the new update doesn't like it. If I delete the python line, the retropie command line and the RetroPie UI work as expected. Not sure what the conflict is, but it's clearly to do with the script on my end.

Below is the autostart.sh if you're curios. Thanks so much for your help!

python /home/pi/scripts/picontrol/picontrol.py&
emulationstation

Maybe a config override for that core?

4.2 is very old release, you should update to a more recent RetroPie version, as we cannot continue supporting such old version.

..near the end I accidentally enabled the mode button on the gamepads and suddenly they worked as expected!

Thanks everyone!

@stattmone If you're using the standalone emulator, then the configuration you've done have no effect. Look in the /opt/retropie/configs/n64/mupen64plus.cfg file and re-arrange the controllers there (look for [Input-SDL-Control1], [Input-SDL-Control2], etc.). The same file is available at \\retropie\configs\n64, if you're using file shares to access your Pi.

I currently don't have another controller.

@lupsyn This post can be close solution can be found here : https://retropie.org.uk/forum/topic/24544/reicast-mapping-controllers-2020-version-stuck/20

Yes, they should work fine.

If anyone else has this problem, it seems that InputAutoCfg.ini is what you are supposed to edit. Changing plugged to false just gave a no controller message. Since I didnt see any section for order, I changed the order of the controller configs but that didnt change anything. However just deleting the nes gamepad section worked and now my bluetooth controller is controller 1. It also stayed that way through restarting.

Take a look at https://github.com/recalbox/mk_arcade_joystick_rpi, it's similar to what you have in mind and it's already included in RetroPie.

@b39_ https://retropie.org.uk/forum/topic/30144/issues-with-retropie-and-brook-wireless-fight-board

update: I think I found the main problem with my config. I installed the joystick selection tool
https://retropie.org.uk/forum/topic/1167/here-is-a-way-to-select-joystick-for-players-1-4-global-or-emu-specific
to check what's been set up for the players.

alt text
Yeah, okay... ;-) No idea what caused that configuration...
I moved The DragonRise Controller to P1 now and set P2-P4 to ** UNSET **

Now, in lr-genesis-plus-gx all keys are working as expected, Retroarch GUI is showing up also! :-)

@NurseAngela what I have is a cheap usb PS2 replica controller which I have assigned as player one for consoles such as N64, PS1 etc that would need the trigger buttons

@quicksilver
It had passed 4 months before I actually tried your fix proposal.
It worked. The X-box controller is now fully compatible. Thank you!

@rodolfoaguilar @Firebird_WS6
I'm summing up what quicksilver proposed.
This solution worked for me.

Plug in a Keyboard While in Emulation Station press F4 to open the Terminal Type sudo nano /etc/modprobe.d/xpad.conf Change
xpad triggers_to_buttons=1 to xpad triggers_to_buttons=0 Press cntrl-x Accept the changes. Return back to Emulation Station by typing emulationstation Restart Retropie.
(In my case, I noticed that the X-box controller had started acting strangely while in Emulation Station.
The D-pad buttons swapped positions in Emulation Station as they were previously in PPSSPP.) Remap the controller in Emulation Station. Remap the controller in PPSSPP if necessary.
(In my case, this was not needed.)

I'm not sure why this issue is affecting some people and not others.
Apparently, the problem is caused by the Trigger buttons somehow.

@mats164 said in Problem with controller mapping being different in games and menu:

@mats164 Could I delete the es_input.cfg.bak as well, and then reconfigure the mapping?

No, that's not the way. You can reset your input configuration through the RetroPie-Setup script - https://retropie.org.uk/docs/EmulationStation/#es_inputcfg-edits.