@barbudreadmon This is INCREDIBLY helpful. Thank you for sharing that link and giving me a breakdown of how I should be handling my ROMs. I appreciate you taking the time!

@abj said in Import ROMs into Mame:

@jak75

This message is the runcommand launch menu, it's not an error message. It's appearing every time you start a game. More info here : https://retropie.org.uk/docs/Runcommand/.

Ok regarding the message I saw, but I can't get the audio, I reset the audio to default settings but nothing to do, it works well with other operating systems, any advice?

@mitu Hi, just a quick follow-up that downloading from source (MAME 0.263) has resolved this error for me as well. Thank you!

@mitu Thank you for the information. I am sorry for posting in the wrong area.

@Muckypaws I think you can do this with core input remapping.

For quick menu > controls > port 2 controls, you want to set the joystick directions to their right stick counterparts, and then set mapped port to port 1. Now the player 2 joystick should behave as player 1 right-stick. Save this as a game remap file and you should be all set.

https://retropie.org.uk/docs/RetroArch-Configuration/#core-input-remapping

@krullbeast said in games i can't get to work on pi4b driving me wakuwaku:

my set-up running MAME 2003 with non-merged 0.78 roms

From my experience, there is a 99.99% chance a part of that sentence is wrong, meaning either you are not using MAME2003 for those games, or you are not using 0.78 romsets for those games, logs would confirm. The 0.01% remaining would be that that your files are corrupt or that MAME2003 simply can't run those games (it'd be surprising but never say never about a MAME game flagged as working properly while it actually doesn't). Which leads to the main question: why you are using MAME2003 on a pi4 to run those games ? There are multiple options that are plain better, almost any other option actually.

@krullbeast said in games i can't get to work on pi4b driving me wakuwaku:

RetroPie Version Used: standalone version in PINN

So what is that exactly ? One of those 3rd party builds that are not supported here ? It would explain a lot about your issues.

@thelostsoul yes, you and @mitu can all make me feel bad for the liberal use of sudo when I shouldn't :) You're right, I don't need sudo. I might have originally saved the collection files in a folder where the pi user didn't have write permissions, so that was that! Or I might have just been lazy about it - also likely.

Yeah, there's no issue with the platform you use, by all means - though you can install RetroPie on a Linux machine as well! A Pi3 is certainly a viable option, though with the Pi4 and the Pi5 - and especially with you playing on a Linux PC and a Steam Deck - the systems it supported are slightly self-contained by now.

No worries, I'm thinking of some developments on the EmulationStation front and this was a fun input that I had not considered. When I get around to it and publish them here I'll tag you.

Cheers, have a great weekend!

@drog1998 whether a rom runs with a particular core ain't depending on the folder (that would decide which (if installed) emulators are available to choose from for the roms therein; for lr-mame-cores those would be arcade and mame-libretro.), but of its content (dumped information within the archive). You need a dump matching the cores requirements (defined/queryable within its dat/xml). Take a look at RetroPies Docs and the libretro docs about romsets. In short you need to aquire or build a rom that matches the core requirements (and don't ask for it, as that would be violating the forum rules).

@barbudreadmon oh I follow you now. And that's nice to know about the mame keys. That will be useful to me shortly.

Thank you again for helping me understand all of this.

Luckily in this instance, it was user error.

@SAVVYSCLUTTER We're not your 'support hotline' so it's useless to tag your topic with 'URGENT'. Don't be rude with the other forum members and don't shout.

Come back when you're ready to talk politely.

@Thorr69 said in Cocktail cabinet woes RPi 4b 8gb:

Your link goes nowhere.

https://retropie.org.uk/docs/Arcade/

Reinstalling RetroPie fixed it.

Reinstalling RetroPie fixed it.

The reason for no buttons lighting up upon entering a rom can be found here (this fix will possibly work as long as you are getting lights flashing while in the retropie menu system):

https://retroarcadebuild.blogspot.com/2023/11/rgbcommander-update.html

BINGO.... I figured this out and was just coming back to say thanks for the SDL tip again. For the record, I added the env variable to "/etc/environment" to make it a system wide change.

Again, big thanks.

If the button is recognized by EmulationStation, then it should work in any Libretro cores - I think you're confusing the 'home key' (keyboard) with 'home button' (joypad).
Please add more info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first - including the exact controller type and model you're using.

@roslof Awesome, thanks for helping

@duglor you are probably right about the nvram being the issue, as for whether making it read only will help or not, i don't know.

this is a (sort of) known issue.

specifically, MAME (not 2003 or any of the libretro cores, but MAME standalone) appears to be faster run via the desktop, than via the framebuffer. some info here: https://retropie.org.uk/forum/topic/28362/enhanced-performance-of-mamedev-mame-in-x11

i wonder if this could be fixed by configuring the launch script to launch MAME within X (on pi only)?

it has been on my list to investigate for years now, but yeah...