AdvMAME in 2021 - on Pi 3 and Pi 4
-
@tango said in AdvMAME in 2021 - on Pi 3 and Pi 4:
@dankcushions said in AdvMAME in 2021 - on Pi 3 and Pi 4:
@tango it's also added via retropie-setup - that's the only real method to add/update emulators to retropie. however we can't really support old versions (and it must be VERY old if it doesn't have lr-fbneo).
How old is "old?" This particular setup was set up just before the pandemic, in January or February, 2020. At the time I downloaded the latest image and, after installing it, updated and upgraded it. I've looked in packages under Optional and Experimental. I did find advmame, 3 versions (including the binary one, which I did install). But I don't see fbneo in there.
lr-fbneo has been part of retropie since 4.5 in 2019: https://github.com/RetroPie/RetroPie-Setup/releases/tag/4.5
it's in main packages, and is pre-installed in the pi 3 image.
Also, when I use
apt search
, I don't see any packages that contain "advmame" or "fbneo" in them. Are the emulators not included in the regular repository?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.
this sounds like a good point to download a fresh retropie image, as you don't really want to lumber your relative with an unsupportable old version, even if it was somehow possible to add lr-fbneo to it.
I decided that last night. My arcade system is on a Pi3B+ and I figured I'd like to do one on a Pi4. The problem is I want to keep my high scores and all the changes I've made to EmulationStation and any configuration changes to games. (For instance, in Vanguard, you can fire in 4 directions, so I changed the config so the buttons for each firing direction made sense in advmame - I want to keep things like that the same in a new system.)
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... -
@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? And am I right that the emulator won't show up on EmulationStation unless I have ROMs in the directory?
I have NeoGeo showing up, so I think I'm confusing the two.
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?
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?
-
@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.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.