mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support

hhromic

yes, I definitively don't fully understand how the input works for the lr-mame2003-plus core, hence why I'm so confused about it. So, thanks for the guidance :)

Just to be clear, there are two separate issues that I'm trying to solve:

stop the core of receiving duplicate input (from RA and internally)
change the bindings as my hardware unfortunately is not standard, e.g. it swaps down and right

If I understand you correctly, I should unbind all RA keys (using "nul" in their bindings) except for the hotkey enable system and leave the core on its default bindings. This will solve 1) but not 2). I believe I still need to do what you say but also remap inside MAME to solve 2), and leave RA out of the rebinding.

What I am missing? Thanks again.

Riverstorm

@hhromic - You shouldn't need focus mode when in the RGUI, not that I can think of anyway. You would want your RA config as all RA based bindings. RA isn't capable of receiving duplicate inputs, the issue is TAB based.

The only time I use focus mode is when I am in the TAB menu to counteract double inputs. I turn on focus for keyboard based input devices, configure the game and when I'm done I shut it off. Focus won't interfere with your controller input so you can configure both at the same time, keyboard and controller based input when in focus mode.

One thing I think that might be confusing. I don't think focus mode is meant to be on permanently. It's meant to be turned on temporarily and then shut off.

The other option what Grant is proposing is instead of setting all your RA inputs to nul you could nul all of your TAB keyboard inputs but leave your controller inputs in TAB and use RA only for keyboard based input devices.

Like you said when you set your directional keys to nul you can't navigate RA so that's not really an option because you need that navigation for all the installed Libretro cores and not just MAME. So you need to focus on how you can correct the TAB input. It's harder to explain than I thought but not really very complicated so once you get the gist of it you'll have an "a-ha" moment.

I do the former vs. the latter and it works well and I am able to achieve both 1 and 2 you listed above.

hhromic

@Riverstorm said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:

@hhromic - You shouldn't need focus mode when in the RGUI, not that I can think of anyway. You would want your RA config as all RA based bindings. RA isn't capable of receiving duplicate inputs, the issue is TAB based.

First, thanks for your answer :).
I fully agree, I definitively do not want to use focus mode normally and I do want RA config like any RA based bindings, same page there. However I don't understand what do you mean with TAB-based duplicate inputs. You mean the menu that appears when using the TAB key? I do also receive duplicate inputs in-game too, for example in a game's service menu I see multiple inputs for single buttons. For example the s key is mapped to two different buttons in RA and the core, hence I receive an input for both at the same time. I believe I have to align the core's internal mapping with RA's mapping?

The only time I use focus mode is when I am in the TAB menu to counteract double inputs. I turn on focus for keyboard based input devices, configure the game and when I'm done I shut it off. Focus won't interfere with your controller input so you can configure both at the same time, keyboard and controller based input when in focus mode.

Just to be clear that I'm using a keyboard-based controller, not a gamepad.

One thing I think that might be confusing. I don't think focus mode is meant to be on permanently. It's meant to be turned on temporarily and then shut off.

I fully agree with that, the game focus mode seems to be a temporary toggle for when you need the core to access the keyboard directly.

The other option what Grant is proposing is instead of setting all your RA inputs to nul you could nul all of your TAB keyboard inputs but leave your controller inputs in TAB and use RA only for keyboard based input devices.

Like you said when you set your directional keys to nul you can't navigate RA so that's not really an option because you need that navigation for all the installed Libretro cores and not just MAME. So you need to focus on how you can correct the TAB input. It's harder to explain than I thought but not really very complicated so once you get the gist of it you'll have an "a-ha" moment.

So, again, when you mean "correct the TAB input", you mean the input MAME receives internally via mapping using the menu that pops with the TAB key?
Indeed all this is very confusing and I appreciate the support :)

I do the former vs. the latter and it works well and I am able to achieve both 1 and 2 you listed above.

Will try more things in hopes of getting a clearer picture of what is going on :) Thanks!

grant2258

@hhromic said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:

ould unbind all RA keys (using "nul" in their bindings) except for the hotkey enable system and leave the core on its default bindings. This will solve 1) but not 2). I believe I still need to

the solution is simple.

set a enable hotkey so you have to press that and the hotkey for the hotkey to access.

assuming youve set up all your binds for p1 and p2 to in ra config.

remove the keyboard defaults from mame they are casuinf double binds as well all will work.

Ill do some code to do an ipac mode when i get time.

that has no keyboard codes set as default the problem is when you press a key it pressing a key and retropad (in this mode because of your retropad binds) as well and the mame default keys that are set cause the problem. This is not the place to discuss it. it a really simple fix

Darksavior

@grant2258 The missing drums from level 2.

hhromic

@grant2258 said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:

@hhromic said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:

ould unbind all RA keys (using "nul" in their bindings) except for the hotkey enable system and leave the core on its default bindings. This will solve 1) but not 2). I believe I still need to

the solution is simple.

set a enable hotkey so you have to press that and the hotkey for the hotkey to access.

Did that, yes.

assuming youve set up all your binds for p1 and p2 to in ra config.

I did too.

remove the keyboard defaults from mame they are casuinf double binds as well all will work.

This is what I can't manage to do. In the TAB menu, where I can rebind the keys, the core is receiving double input, so I can't get rid of the internal key binding.
With a default config, for example it says "P1 Up : UP or RetroPad1 Up", I understand I need to only have "P1 Up: RetroPad1 UP", but I can't achieve this with the double-input. If I use game focus mode, I don't receive the RetroPad1 input and of course doesn't map.

Is there a way to create a default.cfg file with custom bindings manually? The file is not human readable so can't edit it by myself with a text editor.

Ill do some code to do an ipac mode when i get time.

that has no keyboard codes set as default the problem is when you press a key it pressing a key and retropad (in this mode because of your retropad binds) as well and the mame default keys that are set cause the problem. This is not the place to discuss it. it a really simple fix

That sounds exactly like what is needed, I hope you find the time to implement it. No rush though!
Thanks for all the help.

Riverstorm

@hhromic - When I refer to TAB input. I actually launch a game and press TAB (with MAME remapping enabled) so I can access the Input (general) or Input (this game). Maybe an example will help but take what I say with a grain of salt because this is just what I do. I know it's complicated but also it allows for incredible flexibility too so this is just one way. Grant pointed out an alternate way that works also so it's nice to have options.

You might see something like this in the TAB menu option Input (this game).

P1 Button 1 = RetroPad1 B

So when I look at that I know whatever button I mapped on my controller in RA to RetroPad1 B will make my character jump, fire, etc.

Now what I want to do is add say for example left control (LCTRL) from my keyboard-based controller to the MAME TAB direct input. I press enter on the field P1 Button 1 and press LCTRL on the keyboard, it will add LCTRL Retropad1 B, that's not really what I wanted, it's a double input.

So I set it back to the defaults or NONE, turn on focus mode, press enter on P1 Button 1 and press LCTRL again. Now the input shows simply as LCTRL. Now that's perfect so if all I wanted was my keyboard-based controller mapped for an arcade cabinet I am done. Turn off focus mode and exit the TAB screen.

But I also want to keep my controller working so any game I may use either my keyboard or controller so I press enter on the P1 Button 1 field again and press RetroPad B on my controller. (RetroPad B is not literally the B button but what I assigned on my controller to RetroPad B). Now my P1 Button 1 reads like this

P1 Button 1 = LCTRL or Retropad1 B

If I want my character to jump, fire, etc. I can press LCTRL OR RetroPad1 B

Even doing all this you may still have conflicts with RetroPad and MAME TAB "raw" or "direct" inputs so what I do is align my RA inputs to match my MAME TAB inputs. So for example I will set RetroPad B = LCTRL and MAME TAB P1 Button 1 = LCTRL, then the same for button 2, button 3, etc. to avoid these types of issues. You could reverse it also and align MAME TAB to match RA defaults.

Keep in the back of your mind MAME accepts two inputs, RA inputs and "raw" or "direct".

I like to use the TAB input because some of the analog dials, pedals, etc. are not properly implemented or can't be configured in RA so the TAB input is still has necessary function for certain games.

Your questions and thoughts are correct and your close to understanding it I think. Just keep messing around and watch what happens when when configuring and pressing buttons and it will start to make sense.

Unfortunately you can't edit the default.cfg directly, that would be entirely to easy! ;)

hhromic

@Riverstorm That's a brilliant post, very enlightening! Much appreciated.
I have already come across how the TAB menu works so is much easier to understand after your detailed steps. I was thinking on leaving the RetroPad bindings there, but after what you say, yes it might make more sense to leave the direct keyboard bindings only for now, until @grant2258 implements the "blank keyboard codes" set as default.

Unfortunately you can't edit the default.cfg directly, that would be entirely to easy! ;)

Definitively this is way harder than it needs to be :)
Again, thanks for all the help. This is truly a nice forum.

Clyde

@Riverstorm said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:

So I set it back to the defaults or NONE

How do you set a binding to NONE in MAME's tab menu?

Riverstorm

@hhromic - Most of what I know is due to @grant2258 coding these features in to the core and then taking the time to explain them. I just try to explain it differently sometimes or how I've come to understand it.

Also out of habit I do most of my configuring on a wired/wireless keyboard even with an iPAC, Xin-Mo, etc. hooked up at the same time. You need access to the focus key and other management keys anyway.

Riverstorm

@Clyde said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:

How do you set a binding to NONE in MAME's tab menu?

Left, left on the left stick on a controller or double delete on a keyboard. Press enter on the field first. You can try it without pressing enter first and only highlighting the field. It might work but I didn't have any luck that way.

hhromic

@Riverstorm @grant2258 success!
Following @Riverstorm very instructive post, what I did was indeed to only map the "raw"/"direct" input in the MAME TAB-menu and left the RetroPad input out. It is a laborious manual work. This prevents the double inputs as MAME doesn't care about the RetroPad input anymore. Together with binding a "hotkey enable" key, MAME is completely separated from RA's functionality and I don't loose RGUI navigation. Much appreciated!

I still feel that there should be an easier way, like an option for MAME to disable RA's input listening or the "raw"/"direct" input listening (or have both). So looking forward for this aspect to become better.

Thanks you both guys for all the help! :)

hhromic

@Riverstorm said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:

@Clyde said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:

How do you set a binding to NONE in MAME's tab menu?

Left, left on the left stick on a controller or double delete on a keyboard. Press enter on the field first. You can try it without pressing enter first and only highlighting the field. It might work but I didn't have any luck that way.

I also use double ESC for setting the binding to NONE. As @Riverstorm said, you first highlight the input field (with ENTER) and then just press ESC ESC. Then it will display "None".

Clyde

@Riverstorm said in mame2003-plus: hundreds of new games, improved input, features, new bugs - now with runahead support:

Left, left on the left stick on a controller or double delete on a keyboard. Press enter on the field first. You can try it without pressing enter first and only highlighting the field. It might work but I didn't have any luck that way.

Left, left or double delete after enter only restores the default binding for that control, it doesn't change it to NONE. Without enter, nothing happens in both cases. I tried it on mame2003 and mame2003-plus, and with game focus on and off. I updated both approx. two weeks ago.

Why is it different for you than for me? What I am missing?

hhromic

@Clyde try with double ESC. I just did it some minutes ago with latest RA and lr-mame2003-plus.

Clyde

@hhromic In mame2003, double ESC also only restores the default binding for that line. In mame2003-plus, it binds a double ESC to that line. Again, with or without focus.

I may update mame2003-plus and try it again. But that will take some time. :)

hhromic

@Clyde I remember I read it somewhere. For example I just quickly googled: http://forum.arcadecontrols.com/index.php/topic,49164.msg479503.html#msg479503

if I remember, I think you after selecting the button (ENTER) you need to hit the ESC twice quickly to get NONE or N/A.. Try that.....

It's a post from 2006, so that feature seems to be very old. Did you try "quickly" pressing double ESC?
Perhaps you need to clear your default.cfg file? (if you don't care for any existing mapping)

markwkidd

Try navigating to the binding you want to remove in the MAME remapper and pressing the Delete key once it is selected.

Do not press Enter first as if you want to rebind, just highlight that binding and press Del.

hhromic

@markwkidd oh I wish I knew that earlier, I was patiently doing the double-ESC after pressing ENTER for each of the million bindings I didn't need.. took some time X_X. Good to know now! \o/

Clyde

@hhromic I did press Esc twice as fast as I am physically able to. :) Also, MAME does react to it, but not in the intended way. It either binds the double tap (i.e. it shows the bound key two times without any and or or in-between) or it reverts any changes to the default binding, depending on the version of MAME I use.

I would rather avoid clearing the defaults, and I would like to be able to set a particular binding to NONE on the fly if the need arises.

@markwkidd I tried Delete without Enter way before I read about the double keystrokes here. Alas, it doesn't work either (i.e. nothing happens when I do it). I also tried holding down Del for awhile, and also tried Backspace to be sure.

I'm very puzzled about this. 😯 I suspect some nasty little mistake we're all overlooking.