I generally do it to make sure its in the right format. Tools these days have made it pretty redundant, but old habits and all that.

I set input_enable_hotkey to my select key, and it made no difference. I'm guessing I need to rebuild my image as something has gone wrong :(

You might need Namco ROM 5.1 and or 5.4. Download 'm from the known places. My Pi version of Advance Mame needs 'm to play certain Namco games, but the Mame4all version doesn't...

Bear in mind, like others said, that there are quite al lot of Mame versions and each needs it own ROM set to plague us retro-gamers.

Succes. :-)

Facing the same since yesterday, after a very simple modification, splash screen set to custom mp4 video. Not apparently related to any Wi-Fi settings, actually now reverted but issue persists. In brief, the system (RPi3B with retropie 3.7) is networked (scraper works) but it doesn't reply to any ping or ssh requests from other systems (obviously on the same network). I can ssh the Rpi from the Rpi itself. Repeated the Wi-Fi config following method one in the wiki guide but it didn't solve the remote connectivity issue.

[UPDATE] Resolved after upgrading router firmware. Apparently not a problem of the Rpi nor RetroPie.

Two things to try. First you can use a program called SDFormater to format the new SD card and make sure it is clean. Second when you make your backup image you can click the MD5 Hash option and it will verify your copy.

This was the first thing I noticed when I loaded 3.7 for the first time. I always go into retroarch to chance interlace to off. It was already off and I remember saying "oh, thank god!" lol thanks for that!

Thank you!

Actually this is a pretty common problem.

You need to edit the config.txt file. If you insert the MicroSD card into a PC you'll find this file at the root of the SD card. You can edit it with Notepad.

If you're within the Pi OS using SSH or locally, you can find it at /boot/config.txt. You can edit it with Nano.

Change the line hdmi_drive = 1 to hdmi_drive = 2

Reboot if you did this via SSH or locally.

@dankcushions

Yep, fully understood with those comments, good point my suggestion is not mame specific. I completely forgot that lr-mame2003 uses the built in TAB menu which is what you are using for rebinds. It doesn't really affect me which is probably why I can use rebinding via retroarch with no ill effects, as I don't really use save states etc, and my exit emulator button is mapped to escape on my Picade so that never changes. Core input remapping as per what FBA uses would be lovely, but I have read previously that it is not supported in mame2003 so not expecting that to be added anytime soon! :)

Cheers

You can buy special black tape to put over the warning lights in you car. I don't think that would work as well on your monitor. :-)

Just found the setting on my profile that I had to edit, sorry, ignore this!

@wetriner I tried it again too. Didnt get a double entry on the USBGamepad.cfg this time. However when I ran super mario 64 the select button wasnt working again. After checking mupen64plus.cfg I saw it had failed to bind "Joy Mapping Stop" etc again...

No worrys I just enter the values myself, I wanted to understand why 3.7 wasnt auto doing it though yet 3.6 does. Guess I'll never know

From your description, I believe your problem has something to do with switch debouncing issue. Google "switch debouncing" if you don't know what I'm talking about. Most likely it's due to a poorly designed hardware or/and poorly written firmware. You might be able to fix it by using a couple of capacitors + diodes.

Good luck.

Sorry I should have been more specific. When I launch it, as per the wiki, I don't get the option to load anything. When I type "CAT" it tells me that there's no disk inserted.

Thanks, I will try it tonight :)

regarding speed - you may want to compare your results with those on the compatibility lists on https://github.com/retropie/retropie-setup/wiki/Managing-ROMs

if you're getting different results from others, maybe it's a different issue. you don't have a shader on? overlays shouldn't affect performance but shaders for sure can!

/tmp/runcommand.log may show some sort of error, after you get a failed load