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

Clyde

@Riverstorm No problem, I just wanted to tell you that I know the hierarchy in principle, so that you would know what you don't have to explain to me. :)

Here's the summary of my test today after updating RA from binary, as well as mame2003 and mame2003-plus from source.

Esc,Esc sets a binding to none in Input (general). \o/
Left,Left only sets a binding to none if game focus is on. Without game focus, the Retropad left ist bound twice, which is a known problem discussed here.
Del without Enter still doesn't remove the binding ( @markwkidd ).

So, at least the riddle is solved. I still miss a way to remove a binding in Input (this game) regardless if there is a binding for it in Input (general). I know I could edit the config files, but that is rather inconvenient in testing situations to find the best controls for a game.

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

I have a working solution and i will also add support for people wanting to use the old way of mame doing things. I just finished a nightshift so ill get the code done really soon and explain what you need to do then. Sorry for any inconvenience this may cause anyone.

That sounds great, especially the explaining part. :)

update: mame2003 plus esc now works that part of the code has been fixed already. The old code wont no need to update yet ill do the fixes soon

What exactly does work now in contrast to before and/or mame2003? Just trying to avoid (more) misunderstanding. :)

grant2258

@Clyde

everything works mame2003 has the exact same issues with this you assuming you dont have you hotkeys nulled (it wont matter though in thus this case though and you have the default ra pl keyboard settings) start nbbatman in mame2003

press the ra p1 credit key (right shift ) a few times player 3 will start.

I really dont want to get into details here. it will be fixed and the underlying reasons dont matter to the end user.

note this a a keyboard/ipac setup issue that does need addressed

Clyde

@grant2258 As a mere end user myself, I'm perfectly fine with end user level descriptions. :)

In my last post, I just referred to your announcement about explaining what we need to do after you finish your code. Take your time, and thanks for all the work.

grant2258

@Clyde

all you will need to do is set your ipac up in ra config and set an enable hotkey so you dont need to null and hotkeys out nothing more

Clyde

@grant2258 I don't have an IPAC, but two DragonRise controllers and a normel USB keyboard. So, the problems you describe are only occurring with IPAC? Then my apologies for missing that in the discussion. O:)

grant2258

i use the two dragon rises myself :) the problem exits in keyboard too do the above it is for keyboard. I will implement the code and the how to setup. The final decision will be up to mark though

Riverstorm

@Clyde - I also updated from source and I'm have the same results as you. For Input (this game) nothing I tried could set the field to NONE except doing so in Input (general) and inheriting down. :( That's an issue in itself. Deleting a game.cfg every time you want to clear a field is a bit brutal.

@grant2258 - I hear ya but you're going to need TAB input if plan to do any type of NOT mappings but if not I suppose you could just bind in RA and call it good.

I just finished watching the original Halloween and going to catch some shut-eye. I know you wouldn't talk down to us or call us stupid so at the expense of sounding condescending; I'm proud of you and look forward forward to what your plan is also! ;)

grant2258

tab menu will still work it will become clear when it done just trust me

Clyde

In grant we trust. :)

grant2258

@Riverstorm when i say bind to RA it mean you set your ipac keys up in RA config this binds these keys to the retropad. The tab menu will work and your changes will show up as retropad changes not keys just like a controller would this is per spec of what the RA really does.

As you know we have maps for different layout it means one setup will work across cores

hhromic

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

@Clyde - Sorry, I now you've been doing this a long time too. I started the post directed at giving you incorrect information on left/left and del/del and ended the post trying to share more information, that you didn't need. It was meant for @hhromic helping with his setup, sorry about that and have a good weekend.

much appreciated :)
and thanks @grant2258 for addressing and trying to find solutions for us!

Riverstorm

@grant2258 - I fully understand what you are the explaining on how it all works and TAB mapping isn't needed for average cases/users who want to get it up and running quickly or have a positive out of the box experience.

For advanced configurations TAB is needed. The things I am not 100% sure on for RA capabilities are <NOT> mappings, dual joystick mappings (left/up, left/down, right/up, right/down, etc.) the ability to assign multiple keyboard keys or controller buttons to a single input. I do this on several games mainly on the controller but also keyboard, such as assigning both shoulders and triggers to flippers in pinball games or multiple gas pedal options. Whatever is more comfortable for the player and they naturally start using. There are other reasons why TAB is still viable too.

I am MAME centric no doubt. It's what I've known for 20 years or whatever the years are now. It has functionality RA is just not capable of doing at this stage of development.

I know you have something in the oven that smells good but syncing MAME and RA inputs then leveraging TAB has worked for me for a few years pretty well and I am most comfortable there. I like when there's more than way to achieve a goal, even if someone deems it 90 vs 100 efficient doesn't make folks stupid ;), the gaming is still fun regardless and fun is the goal here but I'm definitely curious what you have planned.

Also a side bar but still "Plus" related, can you set a field to NONE in Input (this game) on the current commit? Should I open an issue? Clyde and I are both getting the same results when on the current build and I'm sure it worked on older versions. Needing to SSH or work at the CLI to delete a game.cfg to set a field to NONE is a bit extreme.

Anyway thanks for all the amazing updates.

UDb23

Just found out that Asteroids discrete sounds were significantly improved in version 125 and 142 of Mame. Details here.
Is mame2003-plus already integrating those enhancements ? If not would it be possible ?

grant2258

@Riverstorm no issue needed the defaults are set to something that why they return that the way it should be its not a mistake.

The tab menu will remain Ill be putting a pull request in a bit. I never said at any point the tab menu was going. As you know you can remap in RA as well so both options will still work.

grant2258

https://github.com/libretro/mame2003-plus-libretro/pull/450

instructions there enjoy

grant2258

@UDb23 it would be best to do an issue on github someone might pick it up

Riverstorm

@grant2258 - Thanks, will update tonight when I get home.

Do you have any thoughts on setting a field to NONE in Input (this game)? I tried every combination I could think of on a keyboard and controller but no luck. Even deleting it does no good because it just inherits from Input (general). You can reset it to defaults or change the defaults but you can't set it to NONE. I even tried the @Clyde method of super speed double clicking to no avail but I think I wore off part of the key label.

grant2258

@Riverstorm ive alread expained this is expected it set here

https://github.com/libretro/mame2003-plus-libretro/blob/master/src/inptport.c#L403-L854

i dont get why you suddenly need the set to none now you never did before. Just wait for mark to pull the request you can set the tab menu now. when you use the ipac and keyboard if its mapped in your ra config.

This isnt like the way it was before its very similar to keyboard only accept it retropad only it will make sense when you use it. Unfortunately we just have to wait for the req to be pulled. it basically maps the same way a controller does.

grant2258

@Riverstorm and @hhromic its ready to compile from source instructions here.

https://github.com/libretro/mame2003-plus-libretro/pull/450

let me know how you get on and take it from there. I do understand where you are coming from @Riverstorm when the only solution before was null the keys or use keyboard only.

The keyboard only option can be added back if this fix doesnt suit your needs there is no reason we cant have both. A topic needs started elsewhere for this though

Riverstorm

@grant2258 - Well that was an interesting read/link but I still missed why you can't set a field to NONE. I guess I need it in laymans terms. I figure a bug is a bug so report it. The reasons I report are two-fold. One is because something I use is broken and two simply because it's a bug. Clyde found a bug, I confirmed it and thought it's worth asking. I mean it's an experimental core so why not report them to the core keepers? I've been putting the screws to Plus for considering it a final core and have more bugs to report, should I just skip reporting? I'm not sure what else to say about bugs, you got me. Sooo...does that mean don't expect to set a field to NONE?