mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support
-
@Riverstorm the default is set to l3 in input general if you map in your ra config the menu will open. The reality is mame only used 6 buttons so l2 r2 l3 r3 are possibilities
-
@grant2258 - Ah, I see, so Retropad ignores keyboard input? Keyboard ignores controller input and simultaneous allows both keyboard, controller and RA inputs, hence the double inputs?
What if you wanted to use RA only for both keyboard and controller. That is
Legacy Remapping
set todisabled
? -
no thats input interface = simultaneous
Legacy Remapping enabled == allows you to use the tab menu mame osd like you do in mame to set your controls
Legacy Remapping disabled == use ra quick menu->controls for setting controls its far from complete
-
Let me re itterated when you map keyboard input setting in ra config
it sends that key and a retropad bind you bound it too to the core
mame picks both these inputs up in the core if we choose a mode other than simultaneous it drops the one you dont want. hope that was clear this is so ipac users have options.
in simultaneous mode we accept both
game focus mode disables all ra extra binds sends from the keyboard and keyboard is freed up to work as it should apart from the game focus key
-
@grant2258 - So when Legacy Remapping is disabled does changing Input Interface make a difference?
What's the difference between "setting in ra config" and a "retropad bind"? I think of them as the same thing. Basically going into settings -> input -> user 1 binds.
-
ok lets deal with one thing at a time forget legacy mode == disabled this just disabled the tab menu right now nothing more at the moment.
"What's the difference between "setting in ra config" and a "retropad bind"? I think of them as the same thing. Basically going into settings -> input -> user 1 binds."
yes this correct
-
So what is "that key" and the "retropad bind" is sent to the core. The retropad bind I get but what is "that key" mean?
-
in ra config
input_player2_a = "s"
ra sends the keycode s as it should and adds a retropad2 a joycode
in simultaneous mode in mame
you pressed s and retropad2 a -
When in the TAB menu you see this line:
P2 Button 1 = a or RP2 B or Mouse2 LClick
Is "a" and "mouse click" the other key, whereas, RP2 B is the RA bind, not sure if that makes sense.
-
Ok, so when I see in quick menu -> controls Auto: 9 (N/A), (Key: num1) Start.
The num1 is the RA bind and the 9 is the retropad joycode? I always think of it as binding two keys to one input?
Can you give me an example of where you set the "retropad2 a joycode" or is that both in one line?
-
im lost what are you asking? If you stuggling with this just use game focus mode
-
Sorry I am not quite getting the "retropad2 a joycode". I get the
input_player2_a = "s"
set in my retroarch.cfgI think of binds as RA in the settings -> input or quick menu -> controls but also in the controls menu you can see the controller binds. Like button 9 is select/credits usually on a controller for me but I am taking it the controller is not the "retropad2 a joycode". :)
-
it means button 9 on the controller and keynum1 is mapped to start
is this case scenario keynum1 would sent sent the a retropad start and keycode keynum1
-
If I can get that piece I get the input options now. in dropping one or the other or accepting both.
-
When I think of the RA retropad I think of two bindings, one to the keyboard and one to the controller for each input?
-
ive already told you this when you bind a key to a retropad it sends that key and retropad start bound to to the core.
a real retropad only sends the retropad start when you press button 9
game focus mode stops the retropad start being sent from the keyboard when its bound on so the keycode sends and works like it should.
the keyboard only option tells mame to drop "all" retropad binds
the retropad option tells mame to drop "all" keyboard inputsthis is all options covered so ipac users can choose a setup for them
hope this makes sense to you
-
@grant2258 - Ah, the light bulb turned on, thank you very much. Just more question if it's easy. What do the
Input Interface
options do, if anything, when legacy mode is disabled? -
About 14 things just snapped into place all at once. ;)
-
honestly it will function the same all legacy disabled does at the moment is hide the tab menu and uses separate config files. Its at a stage now where it can be worked on without modes disturbing each other.
-
Ok, I see what you're saying now that makes sense when you say it's incomplete at the moment. There's a way to go on the RA side.
Well dang, I would hate to try and put all that in a manual and have it make sense. Whoever dreamed up RA, all I can say is--wow. I have no idea if it's possible to simplify but you can't deny it's flexibility.
There's a few more pieces that I think I can figure out while actually messing with the configs.
I really appreciate you explaining all you did it means a lot. Heading out here as my daughter and wife both caught Influenza A. I've been clean so far but we'll see in a few days. It's hard not to catch living under the same roof. Thanks again, good sir! ;)
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.