Neo Geo folder - is it worth it?

MrSkyle

@thelostsoul Gotcha! Thanks for clearing that up! So AES bios is the only one I need to make the emulator (lr-fbalpha in this case) run those roms as if they were their console counterparts, correct?
And where exactly should I put the AES bios? Inside the "bios" folder or the "neogeo" rom folder, just like the "neogeo.zip" bios?

@thelostsoul said in Neo Geo folder - is it worth it?:

This is a bit confusing. All you need is a bios containing AES and set it once in Retroarch through AES. Then all games will use this.

Regarding this bit, this will only apply to all games in the "neogeo" rom folder, right? The ones in the FBA rom folder will remain untouched as arcade/MVS versions? Because that's the whole point of creating the separate Neo Geo folder for me now: leave one copy in the "fba" rom folder to run as arcade and another copy in the "neogeo" rom folder to run as console version, set to AES...

thelostsoul

Yes, you put neogeo.zip bios file in the folder with the neo geo roms. In fact neogeo bios is the only bios needed to do that. While I did not not test it out, both folders should work indipendently, so you can have both type of bios, one in FBA and one in Neo Geo. But be aware I did not test it. If I am at home, i can test it for you - but I expect it to be working anyway.

My biggest problem after finding out about all those bios things, I had trouble finding the right one. So be careful.

Edit: Ok, I tested it out and I must say, it does not work (the way we want it). I just copied the same bios file and Metal Slug rom to FBA folder and changed from AES to MVS and checked if it affects the Neo Geo folder games -- and yes, it affects it. They use same emulator with same settings.

After looking in the file structure if I can find any config file for this, I must say I am clueless what to do now. Maybe changing something in /retropie/configs/neogeo/retroarch.cfg and /retropie/configs/fba/retroarch.cfg or in the same folder the file emulators.cfg will do the trick. For now, I don't know more.

thelostsoul

Ok, I found the file where the Neo Geo mode is specified, it's /retropie/configs/all/retroarch-core-options.cfg and the corresponding line to this is fba-neogeo-mode = "MVS". And I have no idea how to make it separate setting for FBA and Neo Geo, as this is in all.

quicksilver

@thelostsoul if you are using Lr-fbalpha I believe you can change it through the retroarch menu. Run a game then press select+x (default). There should be an option to change the bios in there. Just remember to save the core remap when you are done.

AndersHP

I use the Arcade folder for MAME, FBA and ADVMAME as described in this thread, combined with a dedicated Neo Geo folder (all FBA).

The reason for the latter is mainly that Universal XML Scraper lets you get coverart for the Neo Geo games, so this folder looks really neat, like the console folders.

The Arcade games have no coverart, just screenshots and logos.

thelostsoul

@quicksilver Yes, I did it through the Retroarch menu before. The point here is, to have two different settings for same Lr-fbalpha emulator. If I change FBA setting through the menu, it will affect the Neo Geo games too in that different folder, because it is a global setting. Thats because I was searching for a way to change it through some command line parameters or including it in retroarch.cfg.

MrSkyle

Bummer, there goes the plan of having the roms in the "neogeo" folder automatically run as AES and the ones in the "fba" folder automatically run as MVS...

Still, I find solace in what @AndersHP said - having a separate folder for scraping purposes and game covers seems quite nice. Maybe I'll do it anyway and perhaps someday we'll have an option in lr-fbalpha that automatically uses AES settings whenever loading a rom from the "neogeo" folder.

quicksilver

@thelostsoul have you tested saving on a per game basis?

thelostsoul

@quicksilver I did and I am not sure, but I think the MVS/AES setting remains as a global one if emulator is loaded (in said file above). After inspecting the resulting file, there seems no setting saved in there which saves the MVS/AES setting. Also, because I have already a config file for each game, I am not entirely sure. And I fear I would mess up something, if I try more. For now, I just leave it as it is. Looks like an emulator limit.

mediamogul

@thelostsoul said in Neo Geo folder - is it worth it?:

I have no idea how to make it separate setting for FBA and Neo Geo

You can create a file at /opt/retropie/configs/neogeo/neogeo-core-options.cfg the has the line:

fba-neogeo-mode = "AES"

then add the following line to /opt/retropie/configs/neogeo/retroarch.cfg

core_options_path = "/opt/retropie/configs/neogeo/neogeo-core-options.cfg"

After that, whatever arcade system you launch lr-fbalpha from can use the universal MVS core setting at /opt/retropie/configs/all/retroarch-core-options.cfg and anything launched from the Neo Geo system will use the newly created core config file for AES.

thelostsoul

@mediamogul Thank you, I was searching for something like that (not for me, because I am happy with how it is anyway). But in this case, it means two whole different core-options. Would it be possible to just include that fba-neogeo-mode line in a cfg file and include it with #include for overwriting?

mediamogul

@thelostsoul

I've never tried it with core options, but it's worth a shot.

thelostsoul

I just tried it, #include works with core-options files, but...
still ignores the different settings and uses the retroarch-core without overwriting it on the fly. Changes aren't saved in Neo Geo I think and it half way filles that neogeo-core file. In short, its just a mess. Seems not working as expected and the only way would be having two different core options files and that is a no go to me personally. Its just too much trouble.

The last thing I can think of would be to start a script before and after launch of Neo Geo games to change the value on the fly.

mediamogul

@thelostsoul said in Neo Geo folder - is it worth it?:

the only way would be having two different core options files and that is a no go to me personally.

I don't really understand the aversion to this. The settings are thoughtfully put in place to allow the type of functionality you're looking for. Having two files seems like a small price to pay, but that's just me.