MAME2003-plus mapping problem (Solved, see last post)

gomisensei

I am experiencing A LOT of confusion trying to set buttons in retroarch/mame2003plus, specifically in the mortal Kombat games. I have tried both with and without legacy remapping enabled, but whenever i change the keybinds in the quick menu->controls, things go haywire. Like, if I switch 2 of the bindings, neither works except when i press both bindings, then they both light up. If i change all the buttons to bind to one in game button, only one of them works.

I suspect maybe the legacy remapping isn't going away, only access to it in the mame menu? If that's the case, where does mame2003-plus store these settings, so those settings still affect bindings?

This is exasperating, as i've built my system around the mame2003 romset, and can't easily switch to another emulator (and don't want to).

I'm using retropie on a pi4.

mitu

@gomisensei said in MAME2003-plus mapping problem:

I suspect maybe the legacy remapping isn't going away, only access to it in the mame menu? If that's the case, where does mame2003-plus store these settings, so those settings still affect bindings?

Similar to mame2003, the configurations are stored in the mame2003-plus/cfg folder, created next to your arcade romsets. So if your games are in the arcade folder, there should be an arcade/mame2003-plus/cfg where the configs are stored. You can clear that folder to reset the input configuration(s).

gomisensei

@mitu yeah, found that, deleting both default.cfg and the gamename/ra_gamename.cfg didn't actually fix anything with the bindings. Works as it should in other cores, just mame2003-plus has the weirdness. For example, when i map my keyboard to buttons, some of them work, but others require me to press 2 keys together to trigger one but. I went into neogeo test input, mapped z key (B button)to NEOGEO A, x (A button) to NEOGEO B, c (L button) to NEOGEO C, v (L2 button) to NEOGEO D, and ended up with NEOEGO A and B working fine, but NEOGEO D being triggered by s (X button) and NEOGEO C being triggered only by holding both v (L2 button) and a(Y Button). (also, for some reason, L2 is set as turbo button(classic mode), but the buttons don't stop turboing when i let go of them.

I noticed similar problems a year ago on my pi4/tv setup when i tried to remap my ps4DS to a sane configuration (the default doesn't seem to be) but i don't think i ever fixed it, as 1-3 button games seem to work fine.

I even loaded the remap from FB NEO, and it looks fine on the control port screen, but acts as above.

Maybe i messed something up when i was playing with the simultaneous mame input? Where would those binds be stored? if in the cfg files, deleting those didn't reset or fix.

mitu

Can you please add some info about your setup - what input devices are you using (KB/Gamepad/combo) ? Do you have any input overrides for the core/folder ? What ROM are you using to test ?

Get a verbose log and post it on pastebin.com, this should show what options are you using for the core and if any overrides are applied.

gomisensei

@mitu using keyboard (via picadex HAT gpio pins) for p1, usb controller for p2. Using a simple remap for the game, no overrides besides that. Tried with many 4-6 button games, but specifically, metal slug 2 for this example. mk and sf games are even more confusing... Tried with mame2003, works as expected.

pastebin seems to be down, the --verbose output shows only a few input related lines,

[INFO] [Input]: Found input driver: "x".
[INFO] [Remaps]: Game-specific remap found at "/opt/retropie/configs/arcade/MAME 2003-Plus/mslug2.rmp".
[INFO] [udev]: Pad #0 (/dev/input/event0) supports 0 force feedback effects.
[INFO] [Joypad]: Found joypad driver: "udev".

mahoneyt944

Mk game inputs were fixed recently in mame2003-plus, update the core "from source". Should take about 25mins or so, on my rpi3b+ anyhow. Then delete you default.cfg and game.cfg and relaunch any of the mk titles (mk, mk2, mk3 or variants).

mitu

@gomisensei I can't reproduce this, but Metal Slug 2 may not be the best game for this, since it only has 3 buttons. If I use RetroPad as the Input Interface in the Core Options, then the remapping done from RetroArch's Controls menu are applied - can switch A with B for instance.

I tested with a keyboard controller, but i think the same remapping works with a gamepad/joystick.

gomisensei

@mitu said in MAME2003-plus mapping problem:

@gomisensei I can't reproduce this, but Metal Slug 2 may not be the best game for this, since it only has 3 buttons. If I use RetroPad as the Input Interface in the Core Options, then the remapping done from RetroArch's Controls menu are applied - can switch A with B for instance.

I tested with a keyboard controller, but i think the same remapping works with a gamepad/joystick.

i'm compiling the latest source. I suspect there is some lingering mame-binding weirdness going on still, not sure how to freshen/delete the mame-menu keybinds completely.

gomisensei

@mahoneyt944 any idea where mame2003-plus stores the mame-menu keybinds? I tried disabling the legacy remapping, but i feel like the keybinds still remain somewhere, cuz it only got worse as I tried to use legacy binding to fix the problem.

gomisensei

@mitu I tried mkla1 with latest source. as an experiment, i bound every key to "button1", and only one of the buttons actually did the action (low punch), with all 6 other buttons doing nothing. Using trial and error, i managed to set each button to it's "preferred by the emulator" position, and I have all 5 buttons working, but I can't change which one is where or it doesn't work.

mahoneyt944

@gomisensei you probably have a mix of things working against you right now. I would delete all the remaps, all the cfg files, and core options you saved and try from scratch. The location you launch your mame games from will create a folder mame2003-plus filled with lots of sub folders. Just wipe it all out. The remaps I believe are stored elsewhere. Make sure you reconfigure your controller / inputs in the ES menu too. The simultaneous core option you enabled is an option which decides to use only retropad input, only keyboard input, or both (simultaneous).

It maybe beneficial to actually use the mame menu to map the inputs the way you want but a lot of these decisions are based of how you expect things to work.

gomisensei

@mahoneyt944 ok, i figured it out.. When i was first trying to use legacy setting, I had simultaneous controls set, so it would set the legacy with both the retropad (A,B,X,Y,L,R, etc) as well as the keyboard mapping for the retropad. This had the effect of binding both to each assigned button, so when i changed the remap or button in RetroArch, the legacy assignment stayed with both the binding i set, AND what it was bound to in RetroArch when i set it.

Long story short, i turned off simultaneous while binding the legacy keys to retropad assignments, then after setting them, I could set it back to simultaneous so I could use my keyboard controls (for test mode, service, volume, etc) as well as my control mappings.

Thanks for the help, so glad i finally figured this out.
thanks to you too, @mitu