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

markwkidd

Update today: All driver warnings are displayed via the libretro frontend rather than the legacy MAME UI. Not the most exciting development perhaps, but it has a nice finality that I appreciate.

grant2258

Well this is good and bad some messages like working clones should be in a pop up box with user interaction so people have time to read it. But the rest can scroll away np.

just tested moon walker (moonwalk) its not working shows no message about clones. Think the samples are over riding the message or it just not working. If some messages over ride others i think you might want to reconsider using this

ward614

I just wanted to make a quick post here to thank you for adding a 4-way option to Mame2003-Plus! I can't tell you how annoying trying to play Pac-Man has been! I am using Xbox360 controllers with my Pi, and simply turning on this option and setting it to use the d-pad has made many classics much more playable. Thank you!

ward614

Just wondering if anyone else has experienced this issue,

I had time for the first time in a while to work on my build. I was able to install and use LR-Mame2003 -plus, to play Pacman for the first time with some decency thanks to the 4-way controller feature. Later that day, I upgraded my system from Jessie to Stretch, but since then Pacman will no longer load in Mame-2003-plus, even though regular 2003 still works.

Kinda a niche situation, but I figured its worth pointing out and asking is anyone else has experienced something like this.

grant2258

I would recommend you update your setup script and compile mame2003+ again and let it install mame throuhg the retropie scripts part of this install is the configuring if its changed since the update

Clyde

@ward614 If the problem remains after re-compilation, you could run mame2003-plus with verbose logging via the Runcommand menu and then look into the logfile /dev/shm/runcommand.log for any clues. Or you could upload the log to a pastebin service like http://paste.ubuntu.com/ or http://pastebin.com/ and post a link to it here, so that @grant2258 and @markwkidd can have a look at it.

ward614

@Clyde I will have to look into giving that a try.
I'm going to restore to my backup and try making the upgrade to Stretch again, and if that doesn't work, I will run the log.

markwkidd

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

Well this is good and bad some messages like working clones should be in a pop up box with user interaction so people have time to read it. But the rest can scroll away np.

just tested moon walker (moonwalk) its not working shows no message about clones. Think the samples are over riding the message or it just not working. If some messages over ride others i think you might want to reconsider using this

The new message widget system was just merged into RetroArch, although its only available for the GL video driver at the moment. The new message widgets "stack" so we can display more than one at once. This new system uses the same libretro callbacks we use, so there is no change needed in the core for MAME 2003-Plus to start benefiting.

After this functionality reaches the GDI or D3D10 video drivers and I can test it, I'll rework our notification code to make use of multiple messages. I think that will get us back to where we need to be on the driver warnings and clone suggestions.

Edit: Our notifications now look like this video, assuming the GL video driver is in use. https://twitter.com/natinusala/status/1085260327351173120

grant2258

looks good to me hopefully they will add an option to keep the message there till someone presses it and that will fix a lot of problems.

Good news if ra supports your platform really bad news if it doesnt hopefully it will filter through all the platforms its something that is needed.

ward614

@Clyde After doing a reinstall of Stretch, this issue seems to have been fixed. I must have miss-flashed my ad card somehow. Thank you for your help!

grant2258

@markwkidd expect a shed load of these types of issues now https://github.com/libretro/mame2003-plus-libretro/issues/657 this should have been disabled when ra could implement something workable.

ward614

A question for you all,

I am working on enabling use of a mouse as a dial in 2003-plus, and while I figured it was similar to 2003, I wanted to ask what the proper configuration text was for adding to the config file.

In 2003 you use:

mame2003-dial_device = "mouse"

But is it:

mame2003-plus-dial_device = "mouse"

OR

mame2003plus-dial_device = "mouse"

For 2003-plus?

Thanks!

Riverstorm

@grant2258 - There seems to be an issue with the TAB menu input fields are being reset to defaults when you change core options.

If you delete all your cfg files and start a new game. Make changes in TAB menu. Then if you go into the RA core options and change Artwork Multiplier from 1 to 2, exit the core and restart the game the TAB menu options seem to be reset back to the defaults.

I've deleted my default.cfg along with all the other cfg files. I'm on a Pi 3B+ running RetroPie 4.4.8, Plus commit 7c17094 and RA 1.7.5.

grant2258

it will be reset if you change from analog to digital it has too well input general will thats what it changes. I really dont know what you mean reset back to defaults what is the tab menu can you clarify.

there are ony two core options that effect this

changing analog and digital will reset your input general

toggling the legacy remap will disable saving thats why it says restart then your changes will save. ( this will happen if the option is toggled regardless of the original setting)

i have no idea how you will map in none legacy mode they are just kept as defaults ra will need to address that if it wants a none legacy mode mapping it has seperate cfg files and you can only map what ever is in the controllers menu. youll need to be more specific and how to recreate your issue its very vague

grant2258

nm i see it happening ill have a look when i get some time just some logic needs changing was working when i done it strange.

edit
got some time fixed wont change now unless you physically change the input type

Riverstorm

@grant2258 - Here's the steps I did to make it to reset back to the defaults. I would notice my defaults were reset occasionally and it was when I was changing core options but not the analog or legacy options.

Delete all the /home/pi/RetroPie/roms/mame-libretro/mame2003-plus/*.cfg files
Start a game and change the TAB menu option to another key besides TAB (or change any field)
Exit game
Start game
Go to Quick Menu -> Options and change Resolution Multiplier (anything but analog which I know does a reset or legacy)
Exit game
Start game and TAB menu options are reset to defaults

mbrett

OK, I was asked to report my results back on Atari Paddle controllers w/in Plus, and I can't see them. Same as regular MAME. I would need help in mapping them correctly before I could report back results. I am trying in 'Tempest' & 'Warlords'.

grant2258

check your ra logs if picks up as a mouse device change the mouse index to what the paddle/dial is set too. same will apply to any ra core you want to use it in. youll also need to be on retroarch 1.7.6 for mouse support to work.

mbrett

Lemme know if you want whole log. I get this:

[WARN] [udev]: Couldn't open any keyboard, mouse or touchpad. Are permissions set correctly for /dev/input/event*?

[INFO] [udev]: Plugged pad: Microchip Technology Inc. 2600-daptor (1240:64029) on port #1.

[INFO] [Autoconf]: no profiles found for Microchip Technology Inc. 2600-daptor (1240/64029).

That's all I see that could apply to my situation. As I can't find any guides to getting the Paddle to be seen and working outside of standalone Stella (where the emulation is slowed to crawl), I have absolutely zero idea what I am doing.

grant2258

sounds like you need to update your retroarch in retropie you can compile this from source or install from bin im not sure if the bin has been updated or not. It is strange to get the permissions error like that though if you can update your retroarch first then let me know how you get on if you dont know how to do that let me know