Problems Migrating FBA Roms from 3.7 to 4

windjammersfan

I'm having an odd problem with FBA. I had FBA working great in 3.7 but recently backed up my roms and updated to 4 from the fresh image on the site here. I copied everything back over but now nothing works in FBA.

I thought this might be down to rom set changes so I checked my roms and while some of them needed updating most were fine. I seoarated the NEOGEO roms from the others while doing this so that those games were in a NEOGEO section.

My roms were checked with Romcenter 4 beta, so that may be a problem but I doubt it as the NEOGEO games in the NEOGEO roms folder work fine now. It only seems to be games in the fba folder that won't run. I haven't tested everything but it's the same result across a variety of games that all worked in 3.7.

dankcushions

@windjammersfan fba romsets could have changed. lr-fba-next went from FBA set v0.2.97.37 to v0.2.97.38 a while ago. or maybe you were using lr-fba (0.2.97.30) or pifba (0.2.96.71) back then, and now are using lr-fba-next (the current default).

windjammersfan

I removed all the roms in my fba folder and did a quick test. I know that the neogeo games work fine, so I assume that a neogeo game supported by lr-fba-next should run in either the fba or neogeo folder providing both folders have the bios too. Unfortunately this doesn't work. The same dame, the same emulator, different results.

What I think may have happened is when I migrated to 4.X I copied the config files I had for custom button remaps on fba games. Is there anywhere I can download a copy of the original config files that would have been in the /opt/retropie/configs/fba folder?

dankcushions

@windjammersfan said in Problems Migrating FBA Roms from 3.7 to 4:

I removed all the roms in my fba folder and did a quick test. I know that the neogeo games work fine, so I assume that a neogeo game supported by lr-fba-next should run in either the fba or neogeo folder providing both folders have the bios too. Unfortunately this doesn't work. The same dame, the same emulator, different results.

fba and neogeo folders do not necessarily have the same emulator. you can set both to different emulators via the runcommand. you should use the runcommand to confirm what emulators you are using for your test game.

https://github.com/retropie/retropie-setup/wiki/runcommand

What I think may have happened is when I migrated to 4.X I copied the config files I had for custom button remaps on fba games. Is there anywhere I can download a copy of the original config files that would have been in the /opt/retropie/configs/fba folder?

if the games are simply crashing out then i wouldn't have thought this could be an issue. in any case, retropie normally creates a backup called retroarch.cfg.rp-dist (or something like that) in that folder. you can rename that to retroarch.cfg and it should revert to the default, but it depends on how you remapped the games.

windjammersfan

Both fba and neogeo folder are running lr-fba-next. My fba configs folder (/opt/retropie/configs/fba) has the following files:
emulators.cfg
retroarch.cfg
content_history.lpl
(I may have read them wrong but you'll probably recognise the files.)
There's no other files there, no backups or anything.

At this stage I'm thinking about restoring from the clean image of Retropie 4 and copying over the games again, taking time to be careful about the fba roms and leaving the config files alone until I know the games run.

dankcushions

@windjammersfan like i say, i don't see how it can be configs if games are crashing out. that only happens with lr-fba-next the rom and or bios are wrong. can you give an example of a game and what happens when you run it? double check it's definitely running lr-fba-next in both cases and that the filesize (well, SHA1/crc) of neogeo.zip and the rom are the same in both folders.

windjammersfan

I've just got everything working again from a fresh RetroPie 4 image. I've no idea why the fba games didn't run before but all I did differently this time was not copy the contents of my fba config file as mentioned above. That probably was the cause.