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

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

mbrett

@grant2258 I am on 1.7.6. But when I try to update from source I do get a slew of error messages.

Log:
https://pastebin.com/851bvjcp

I don't know what that all means.

mitu

@mbrett You're not connected to the internet ?

git clone --recursive --depth 1 --branch v1.7.6 "https://github.com/libretro/RetroArch.git" "/home/pi/RetroPie-Setup/tmp/build/retroarch"
Cloning into '/home/pi/RetroPie-Setup/tmp/build/retroarch'...

fatal: unable to access 'https://github.com/libretro/RetroArch.git/': Could not resolve host: github.com

mbrett

@mitu BWAAHAAHAA!!!

Indeed I was not. Watching one minute of the Oscars shall turn anyone's brain into mud.

mbrett

@grant2258 OK, I received the exact same messages in log after updating from source.

markwkidd

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

@grant2258 OK, I received the exact same messages in log after updating from source.

Just to be sure, did you update both RetroArch and the emulator core?

mbrett

@markwkidd Well, no, I didn't update lr-mame2002plus since updating retroarch. I shall do that and try again.

grant2258

upload your full log to https://pastebin.com/ pasting two lines doesnt help much I still get the feeling your retroarch isint updated

you need to do this run retropie setup

then update retropie-setup script ( this will allow your ra to update to 1.7.6)

after youve done this

goto

manage packages -> retroarch -> update from source

mitu

FWIW, the binary package also has 1.7.6, so there's no need to re-compile from source for RetroArch. That is if you're on the 4.4 (Raspbian Stretch) image.

grant2258

ah ok wasn sure if it was updated thanks mitu just update from bin then.

I will say any time your run retropie setup its a wise move to update your setup script this avoids problems that have been fixed already

markwkidd

Ah yes I forgot that RetroPie-Setup has to be updated first.