@barbudreadmon that's fine, I got it to work. Thank you for your work on FBNeo! I appreciate all that you contribute.

@tango said in AdvMAME in 2021 - on Pi 3 and Pi 4:

@dankcushions said in AdvMAME in 2021 - on Pi 3 and Pi 4:

lr-fbneo has been part of retropie since 4.5 in 2019: https://github.com/RetroPie/RetroPie-Setup/releases/tag/4.5

It wasn't showing up in my emulators, either in EmulationStation. I'm trying to remember from what I've read. Is ~/RetroPie/roms/fba the directory for fbneo ROMs?

yes (and /arcade and /neogeo - see https://retropie.org.uk/docs/FinalBurn-Neo/ )

And am I right that the emulator won't show up on EmulationStation unless I have ROMs in the directory?

that’s right. however you’ll still see it as installed in retropie-setup’s package manager regardless.

i can't stress enough that apt is nothing to do with emulators in retropie :) emulators are installed and updated via the retropie-setup script, not apt. even if they are there somewhere, apt wouldn't install to the same place as retropie, leverage retropie's config scripts, or add the systems to emulationstation, etc.

Okay, that helps a LOT, since I've been bumbling around here, on and off, for a while, and never realized these packages were handled separately from apt.

How are they updated, then? Do I need to update them manually through the script or are they updated automatically?

https://retropie.org.uk/docs/Updating-RetroPie/

My thought would be that if I use a new image and copy the /home/pi/Retropie directory recursively to the new image, that should preserve all the settings, configuration changes, and high scores to the new system. Please let me know if I'm wrong on that.

it wouldn't. for example, (most) config files are stored in /opt/retropie/configs/* etc. You can probably find some info on copying configs across images elsewhere on the forum, or perhaps someone will reply. personally i don't like to copy configs across from older versions - defaults change, emulators change, etc. I think you can end up carrying sub-optimal settings through to later versions. I like to start fresh, or pick and choose specific config files I know to be safe, but that's just me...

With Debian, I can easily do automatic updates so I don't have to go into a system and do admin work. I used to do that when I ran a business where all my software was on a Debian server. I know some people don't like auto-updates, but I never had a problem with things failing or crashing and that way I only had to deal with doing it manually when doing a dist upgrade.

For an arcade system, I'd like to keep that as automated as possible. I have had very little free time in the past decade and I'd rather automate whatever I can.

So how would I handle that with RetroPie, EmulationStation, and the emulators?

the update link above describes how you update retropie, but before we were talking about what was described as a pre-fbneo image, which would indeed be a dist-upgrade (or 2), which is not a supported in-place upgrade.

@sirhenrythe5th
I think I solved it by disabling display_magnify in the .rc

Please note some games appear to have the wrong aspect. gdarius and gdarius2 seem to be vertical, but videos on youtube appear to show them 4:3. This is unrelated to the setting above I think. I don't know enough about stv games tbh.

@fadangalini

Well that disabled the onboard, but still no audio...
I can only laugh at all the problems I keep getting!

@wjkoontz said in Advmame tab menu not accepting input from any device:

Thanks for helping!

Not sure how I helped :), but glad it's working.

I don't routinely use advmame, but I did a few tests and it looks like - when mapping the input - there is a delay between pressing an input and the corresponding key being displaying in the menu. If I do a simple/single press, nothing is shown, but after the input timeout elapses, the input dialog shows the input has been acknowledged and configured. It's like the UI doesn't update immediately after 1 event processed.
We'll see if something can be done to make the input mapping more responsive.

@mitu
Thanks. That did the trick!

I hadn't thought of configuring the trackball to actually be the spinner.

Both advmame and advmess configuration files are under $HOME/.advnance - named advmame.rc/advmess.rc. Game specific configurations are saved there, prefixed with the game/romset name.

I have a Pi 3b and SI95 runs absolutely horribly in lr-mame2003 and lr-mame2003plus, which is why I was running it in AdvMAME in the first place.

We don't support 3rd party images, especially the ones pre-loaded with ROMs. Ask the seller/scammer that sold you the device.

Hi,
all of them... well the three available for retropie... tried with all of them and there is not a way to change video option beyond the offered by mame itself :( maybe there is an option to edit its reg (i must say i am newbie on raspberry )

That's a good suggestion. I added some notes on persistent device paths.

@mitu thanks again - it worked! it actually worked without the "" surrounding the path of the subfolder (and wouldn't work with the "").

@grant2258 Thanks Grant. I can't understand what's in that link, I'm afraid....beyond my pay-grade. But I'm OK with using the USB keypad to make it work.

@gomisensei said in AdvMame - Looks Pretty, Does Nothing:

@Tango If you set up button1 in input(general) it will work for all games that use the first button. Same with each button, digital axis, analog axis etc that you setup.

You can also set up single unique-per-rom inputs under Inputs(this game) that will not carry over, but will overwrite the general inputs for the rom you set it up in only (not sure about clones).

Cool! Sounds like just what I want.

Thank you.

@andrewsi starting it from gdb inside a ssh session could work to have text mode, unless you tried that. But could be it wont break on correct location either then. Not used gdb that much for such problems

The Pi4 support is currently being worked on, the advmame module is not currently - as-is - compatible with the PI4.

@sirhenrythe5th no reason other than 0.94 was listed on the compatibility chart i linked to and it worked for me. i use lr-mame2000 for most mame games on the GPi (pi zero w).

great - thank you!!

@paulr Yeah it's a tough one to navigate. I have the same situation going on and have found nothing so far to help me resolve the issue. Have you found anything?