@mitu Thanks for your reply! I ended up removing the cfg files for the arcade button mapping and re-did the process. Success!

Thanks again

For completeness, I've done some more work...
I checked fuse.rmp, it did not have the "-1" settings applied to anything.
Each game remap would have been created from the fuse.rmp (using the retroarch menus.)

I then checked all my game remap files. 13 of 28 files had this problem.

Next I tried to recreate using the retroarch controls menu.
Cycling right through the available options that can be mapped to the port 1 controls I have:

"---"
Up (1)
Fire (1)
Keyboard Overlay
Up (2)
Down
Left
Right
Fire (2)
Fire (3)
Enter
Space
Then back to "---"

The (1) etc are my addition, "Fire" appears 3 times, "up" twice.
I set some buttons to each of these values, wrote a game remap file and checked for "-1". None of these options generated the "-1".

Next I cleared the options on buttons A, L, L2, R, R2 & X (all originally set to differently) and bingo, I recreated the problem :

input_libretro_device_p1 = "257" input_libretro_device_p2 = "0" input_libretro_device_p3 = "259" input_libretro_device_p4 = "0" input_libretro_device_p5 = "0" input_player1_analog_dpad_mode = "1" input_player1_btn_a = "-1" input_player1_btn_l = "-1" input_player1_btn_l2 = "-1" input_player1_btn_r = "-1" input_player1_btn_r2 = "-1" input_player1_btn_x = "-1" input_player2_analog_dpad_mode = "0" input_player3_analog_dpad_mode = "0" input_player4_analog_dpad_mode = "0" input_player5_analog_dpad_mode = "0"

There appears to be a bug. When clearing a mapping using the retroarch "Controls/ port X Controls" menu from any value to "---" the resulting remap file contains "-1" for that key and this stops you mapping the button using the Retroarch "Options" menu.

I hope this helps repay the debt a little!

@dankcushions what is the best way to do the intial config? Set it up for LR-MUPEN, then customize the mupen64plus config file?

Just a quick update, and maybe a helpful suggestion for others.

I ended up hard-wiring button pairs in parallel and attaching them to the same port :

Controller 1 (numbering according to the above diagram)
J1_8 and J1_5 => left shoulder
J1_9 and J1_4 => right shoulder
J1_7 and J_11 => select
J1_6 and J1_10 => start

Controller 2
J2_6 and J2_8 => select

Thanks to everybody for help!

@tim-s-up Glad you got it working, @lostless is the one that provided the solution though :).

@saccublenda Thanks. Don't have a keyboard plugged on my bartop so I will use the Quick menu / options solutions...I can live with that.

Thanks.

@kjgregory83 you might want to try out redream. For now it has better performance/compatability on the pi 4 then flycast does and controller mapping is a breeze.

@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.

@mitu I have the exact same issue (I made a post about it [here(https://retropie.org.uk/forum/topic/26598/problem-with-controller-mapping-being-different-in-games-and-menu)). If you’re able to help: I use a RPi 3 b+ with a pre made SD image (v. 4.6) from the official Retropie website. I am using a wireless Arrogant Bastard controller with dongle.

@dwarfboysim any update?

@dthgti said in Launch script with Joystick:

but, how do i autostart that on every boot?

triggerhappy runs as a service when your system starts. Unless you've disabled it, it should read the configuration file and do the actions configured.

I will guess that you must be using the latest retropie, and since the way reicast now handles joysticks, the reicast-joyconfig method commonly found on youtube that everyone is trying, no longer works. The docs need updating, but here is where I found the solution for my similar problem after first installing retropie on my pi3b+:

https://retropie.org.uk/forum/topic/24544/reicast-mapping-controllers-2020-version-stuck

I think that thread should be stickied until the documentation is updated. Note that the bottom line for me was the reicast autoconfig (which uses es joypads) chose the wrong device id#'s in emu.cfg. The reicast-joyconfig did what it was supposed to for my 4 controllers, and created working evdev device files in reicast/mappings/. So all I had to do was change the bottom[input] part so the "players" lined up with the right "device id's". In my case I had keyboard=0, mouse=1, joyou dual arcade=2, joyou dual arcade=3, and xbox one s=4. I initially -1'd the keyboard and mouse, and had 3 players configured, but that didn't work at first (+start reicast wouldn't respond). I went back to emu.cfg and -1'd my player 3 (the second half of the joyou), and reicast responded fine showing both player controls... and games also worked 2 player. I haven't gone back and tested re-enabling player 3, but I wonder if having the dual arcade device may not work out with that.

So bottom line, if you ran the joystick config script, you probably already know which device id #'s need a player # to go with them in emu.config [input] section (the rest get -1'd out). More than likely the proper working evdev files are already in your mappings folder, so after getting your 0 and 1 behind the proper = sign in emu.config you should be good to go.

@herb_fargus Perfect; thanks a lot !

@v-roshpi Contact the seller ? You can download RetroPie from our site, and try and get that to work but you will need to contact them for configuration unless you know what it's using to interface etc