Unable to configure per-ROM input override for MAME

mitu

@fidelio said in Unable to configure per-ROM input override for MAME:

I was able to launch RGUI within sf2 and produced the following sf2.rmp file. RetroArch confirms this is loaded when launching the game.
[..]

The remap refers to gamepad's buttons, while your original configuration had a keyboard override. Is your iPAC configured as a keyboard or gamepad ?

Regarding your game .cfg file, you shouldn't include the main config file at the end of it, since the main config file is loaded automatically.

Please provide also some information about your system, as asked in https://retropie.org.uk/forum/topic/3/read-this-first. A verbose log might shed some light on what remaps/configs are loaded by RetroArch when you start the game.

Fidelio

@mitu said in Unable to configure per-ROM input override for MAME:

The remap refers to gamepad's buttons, while your original configuration had a keyboard override. Is your iPAC configured as a keyboard or gamepad ?

It is configured as a keyboard. In fact, I believe that's the only permissible configuration for this IPac (pre-2015 PS/2 I/O version). I should note that the RetroArch in-game control remapper saved the rmp file in the gamepad format.

I also changed the configuration keys in the rmp file to the keyboard-based strings as in retroarch.cfg, but that reverted to the default behavior (suggesting the configuration keys were ignored).

input_libretro_device_p1 = "1"
input_libretro_device_p2 = "1"
input_player1_analog_dpad_mode = "0"
input_player1_a = "0"
input_player1_b = "1"
input_player1_l2 = "-1"
input_player1_l3 = "-1"
input_player1_r = "8"
input_player1_r2 = "-1"
input_player1_r3 = "-1"
input_player1_x = "11"
input_player1_y = "9"
input_player2_analog_dpad_mode = "0"

I also replaced both the keys and values in the rmp with those from my per-ROM configuration and observed the same effect.

input_libretro_device_p1 = "1"
input_libretro_device_p2 = "1"
input_player1_analog_dpad_mode = "0"
input_player1_y = "ctrl"
input_player1_x = "shift"
input_player1_l = "x"
input_player1_b = "alt"
input_player1_a = "space"
input_player1_r = "z"
input_player2_analog_dpad_mode = "0"

Please provide also some information about your system, as asked in https://retropie.org.uk/forum/topic/3/read-this-first. A verbose log might shed some light on what remaps/configs are loaded by RetroArch when you start the game.

Pi Model or other hardware: 3 Model B
Power Supply used: 9V 2A via 5V buck regulator
RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest): 4.7.1
Built From: RetroPie pre-made image from website; updated core packages and emulators
USB Devices connected: USB keyboard
Controller used: custom arcade controller via pre-2015 IPAC2.
Verbose log: https://pastebin.com/t1mwtpCp

mitu

@fidelio said in Unable to configure per-ROM input override for MAME:

It is configured as a keyboard.

In this case, the .cfg game overrides from the docs should work:

input_player1_y = "ctrl"
input_player1_x = "shift"
input_player1_l = "x"
input_player1_b = "alt"
input_player1_a = "space"
input_player1_r = "z"

input_player2_y = "a"
input_player2_x = "w"
input_player2_l = "k"
input_player2_b = "s"
input_player2_a = "q"
input_player2_r = "i"

config_save_on_exit = false

Your log doesn't show the game's .cfg being loaded - I assume you delete it ?

Fidelio

@mitu said in Unable to configure per-ROM input override for MAME:

In this case, the .cfg game overrides from the docs should work:

Thank you for your help, but unfortunately the prescribed .cfg produces the same effect as the other suggestions:

Only the LR button is captured in the game.
Other buttons are captured only when adjacent buttons are pressed simultaneously.
All button inputs work when the overrides are removed, but are in non-ideal locations.

Here is a log of the output with only the prescribed sf2.zip.cfg file in the roms folder: https://pastebin.com/bGnnfgdK

Your log doesn't show the game's .cfg being loaded - I assume you delete it ?

Yes, I removed it during that test to isolate changes. During this test, I tried running with only the .cfg and also with both the prescribed .cfg and .rmp files, but did not observe any changes to the above behavior.

Contents of sf2.zip.cfg:

input_player1_y = "ctrl"
input_player1_x = "shift"
input_player1_l = "x"
input_player1_b = "alt"
input_player1_a = "space"
input_player1_r = "z"

input_player2_y = "a"
input_player2_x = "w"
input_player2_l = "k"
input_player2_b = "s"
input_player2_a = "q"
input_player2_r = "i"

config_save_on_exit = false

mitu

Can you also post your main retroarch.cfg from /opt/retropie/configs/all to pastebin.com ? I don't have an iPAC, but I can use a keyboard to replicate the settings.

Fidelio

@mitu said in Unable to configure per-ROM input override for MAME:

Can you also post your main retroarch.cfg from /opt/retropie/configs/all to pastebin.com ? I don't have an iPAC, but I can use a keyboard to replicate the settings.

Linked: https://pastebin.com/GXqu8zNc

Out of curiosity, I performed a diff of this file and the backup from the distribution and there are very few differences: input1 and input2 settings, and hotkey selection, among some other small things.

mitu

That's weird, it seems to work for me.
Here's the default mapping, as presented in the RetroArch's Controls menu

After applying the re-map (via the sf2.zip.cfg file), the new mapping is reported fine - and you can easily see they're applied since the navigation in the RetroArch's menu is using the new input for A:

I'd say check if the arcade's system config for RetroArch (retroarch.cfg) is set to default and also that you don't have any specific input settings set through the MAME's own menu - delete the arcade/mame2003/cfg/sf2.cfg file and retry the game.

You could try another game or another arcade emulator (lr-fbneo or lr-mame2003-plus) and see if you get the same behavior.

Fidelio

@mitu said in Unable to configure per-ROM input override for MAME:

That's weird, it seems to work for me.
After applying the re-map (via the sf2.zip.cfg file), the new mapping is reported fine - and you can easily see they're applied since the navigation in the RetroArch's menu is using the new input for A:

I was able to confirm this as well. Each time I modify either of the remapping files (.cfg or .rmp), the changes are reflected in the depicted menus. That said, the issues I mention arise during game play. Were you able to play the game with the input remapping?

You could try another game or another arcade emulator (lr-fbneo or lr-mame2003-plus) and see if you get the same behavior.

Thank you for this suggestion as it shed light on what may be happening. All other games I tested under mame experience the same problem with remapping, but not with FinalBurn-Neo. I suspected some conflict was causing this and now I'm certain it has to with some mame key-mappings. I deleted the mame configuration from the prescribed folder but that had no effect. I also tested with the default distribution version of the global retroarch.cfg with the same negative results.

At this stage, it might be easier for me to just use FinalBurn-Neo but I'll see if I can track down where this conflict with mame is coming from. To the best of my knowledge, all other configurations are in their default state, except for the global retroarch.cfg.

mahoneyt944

Have you tried bypassing the retroarch cfgs and just using the mame menu remapping directly? Retroarch main menu-> quick menu-> options -> display mame menu.

Input general are the global configs
Input this game are game level configs

dankcushions

However, I'd like to introduce some overrides via RetroArch as the default button mappings do not properly line-up with standard Street Fighter button arrangement.

point of order, but they do, but it relies on you using the correct physical location or your buttons:

B A R
Y X L

as for your rebind issue - you may have a per-game or global mame internal override that is present. see here for how to delete them: https://retropie.org.uk/docs/lr-mame2003/#mame-menu

mitu

@fidelio said in Unable to configure per-ROM input override for MAME:

I was able to confirm this as well. Each time I modify either of the remapping files (.cfg or .rmp), the changes are reflected in the depicted menus. That said, the issues I mention arise during game play. Were you able to play the game with the input remapping?

With lr-mame2003, I have not.
I have a homebrew image for PS1 that works like an input tester, with a graphical gamepad (PS1 gamepad) image that shows which inputs are pressed. I use it to test any input configuration (it has almost all buttons supported by RetroArch) and testing the .cfg with it worked without issues.

Fidelio

@mahoneyt944 said in Unable to configure per-ROM input override for MAME:

Have you tried bypassing the retroarch cfgs and just using the mame menu remapping directly? Retroarch main menu-> quick menu-> options -> display mame menu.

Input general are the global configs
Input this game are game level configs

Yes, this works fine. I was hoping to avoid this as I have several Street-Fighter-style games that use the same mapping, and I didn't want to configure every single one manually. The config file copy is ideal, unless I can copy mame's binary config file the same way.

Fidelio

Thank you everyone for your feedback and suggestions! I think I figured out what is causing the conflicts I am experiencing, for which I'll reference the following screenshot of the mame input configuration for sf2.zip:

My rebindings are attempting to "relocate" buttons, assigning buttons 1->2, 2->3, 3->6, etc... (as noted before). The end result is that only the RetroPad bindings changed, not the keyboard key bindings. The OR clause in the mame mappings thus maps one key/button to two events and that ends up breaking things!

@dankcushions said in Unable to configure per-ROM input override for MAME:

point of order, but they do, but it relies on you using the correct physical location or your buttons:

B A R
Y X L

I had not considered this, but this seems very sensible given mame's default inputs (key or retropad event). I had have wired things using the IPAC switch numbers, which won't be hard to change.

1 2 3
4 5 6

EDIT
Here is a post descripting this same problem, which is due to the "simultaneous" core input setting in retroarch:

https://retropie.org.uk/forum/topic/29976/mame-button-mapping-conflicting-with-retroarch-button-mapping