@Ashpool thanks for the reply! ... you've helped me rule out some things and gave me more to think about and research. I'm determined to get RetroArch working seamlessly with both a keyboard and my arcade controls (none of which resembles a gamepad go figure!)

@dcaputi said in moving mame back to lr-mame:

So ignore all that and just tell me, should I give FBNeo a try?

Unlike MAME's OSD, RetroArch's Quick menu > Controls isn't good at remapping anything to anything. I have a feeling this might be a problem with your setup. Make sure you read this if you want to try anyway.

And yeah, a lot of games supported by MAME 0.274 aren't gonna be supported by FBNeo, especially 3D games. As for the differences between both emulators, they are explained here and there.

@barbudreadmon
I figured it out.. it was older retroarch mame cfgs
in the retropie configs folder.
I deleted them and it came right on.
No sound problems, no black screens.

@roslof This reply is amazingly detailed, thank you for taking the time to write this up. End result: your instructions helped make everything work perfectly and I am now able to run the older versions of lr-mame. Thank you again!

@roslof thank you so much for providing the binary (once again) and for reporting back re tmnt2! Much much appreciated. I'll keep on testing and reopen the thread should I find anything else.

Libretro mame master branch has been updated to 0255.
Compiling for arcade and mess sub-targets has been implemented again.

Hopefully everything will work like it did before.

It's possible to add and change rompaths in the runcommand loader.

This is a full example from what is installed with my module-script :

lr-mame-basename = "/opt/retropie/emulators/retroarch/bin/retroarch --config /opt/retropie/configs/arcade/retroarch.cfg --appendconfig /opt/retropie/configs/arcade/retroarch.cfg.basename -S /home/pi/RetroPie/roms/arcade -s /home/pi/RetroPie/roms/arcade -v -L /opt/retropie/libretrocores/lr-mame/mamearcade_libretro.so 'mame -cfg_directory /opt/retropie/configs/arcade/lr-mame -c -ui_active -rompath /home/pi/RetroPie/BIOS/mame;/home/pi/RetroPie/roms/arcade/ '%BASENAME%''"

You probably can use parts from above runcommand to add the rompaths to your runcommand.
I would focus on this part :

'mame -cfg_directory /opt/retropie/configs/arcade/lr-mame -c -ui_active -rompath /home/pi/RetroPie/BIOS/mame;/home/pi/RetroPie/roms/arcade/ '%BASENAME%''

Or you can use my project and ,depending on what you install, use the rompaths that are generated for the specific system or category.

Edit:
Also read this for using commandline options :
https://docs.mamedev.org/commandline/commandline-all.html

reserved/WIP (just in case),please proceed!

@barbudreadmon

Good for you ;-)

@eberhab

Ok,
Good find !

You're not going to get any good performance on 3D mame games on the Pi.
But for Soul Calibur and all other arcade games that run on a Naomi or Atomiswave board use Flycast.

It's been a while since your post, but I wanted to offer some insight. I had the same issue with using cheats in Retroarch MAME, and it took me a while to figure it out. One thing I want to point out is when you’re playing a game, you can enable cheats through the Retroarch menu by setting “Enable cheats” to On. Alternatively, you can enable cheats globally by editing the configuration file to include the line mame_cheats_enable = "enabled".
If you’re into more advanced game hacking, you might want to read this guide on kernel-level injectors. It has a lot of useful information.

@mitu said in lr-mame & lr-mess binaries:

Latest commit on the upstream repository is from May, 27 - I think the binaries are pretty close to the 'lastest version'. You can check when the binary was built and from which commit, just to compare with the upstream repo (https://github.com/libretro/mame).

Ah, I see that now. Looks like they're dealing with one heck of a pull request. I'll keep an eye on the upstream repo. Cheers, and thanks!

As the name implies it's basically CHDs (Compressed Hunks of Data) are typically any type of "rotating media" of the day, like a CD/DVD/Laser Disc/Hard Disk. Basically an image that is used along with the ROMs. I think the MAME core folks developed the CHD format.

They are just games that have more detailed graphics, more audio, better processing, better whatever...streaming graphics, streaming audio, etc. requiring more space than a ROM chip can hold. I think Killer Instinct used FMVs (one of the 1st?) and Carnevil streams a good amount of the game as it was digitized footage. I imagine it's more about a particular games "demands/requirements" and less about it being CHD based. I don't think the overhead of accessing the image alone is making it "unplayable".

@jimmyfromthebay The MAME libretro core has a subpar libretro implementation and a lot of bugs because of it. It should be avoided whenever a game is supported by one of the recommended arcade libretro cores (FBNeo, MAME2003+). FWIW, FBNeo supports those 2 games and has a working dipswitch to toggle between single and dual screen.

System apfm1000 is working :
https://retropie.org.uk/forum/topic/29682/development-of-module-script-generator-for-lr-mess-and-mame-standalone/634
https://retropie.org.uk/forum/topic/29682/development-of-module-script-generator-for-lr-mess-and-mame-standalone/650

@johnodon The driver status indicates that the game should be fully playable, however it doesn't prevent the possibility of regressions or other issues, that's your job as a user to report such issues to the emulator authors. Take the color/sound/graphics status in mame with a grain of salt, i know of several issues that i reported myself but it seems they weren't fixed nor had their status updated.