veeshan28

playpopo said I am trying to use RetroArch 1.3.2 to run NeoGeo and got into same problem as op. Here it the solution I found 1. add -L "cores\fb_alpha_libretro.dll" to Associated Platform and check Default Emulator 2. uncheck the "Extract ROMS archives before running" Yooooo, that did it! For some reason "Extract ROMs..." WAS on by default. Never touched that box until now, but after unchecking it, its loading right up. Thanks so much! :)

SentaiBrad said If you need any more help, we have tutorials on our YouTube channel. Click the link in my signature. Thanks Brad. Your 'easy setup' video was a huge help for me with getting the basics going a few days. Unfortunately it doesn't look like any of the videos quite relates to the FBA setup yet. I've tried gleaning some extra tips from a few others, but haven't gotten any further.

Thanks for the responses everyone! I'm determined to figure this out. So far I've tried 3 cores, fb_alpha_neo_libretro.dll, fb_alpha_libretro.dll and fba_libretro.dll. None of those 3 do anything in Launchbox, but all 3 work in Retroarch independently. Can anyone with a functioning setup show me their Retroarch settings under the Edit section? "Emulator Details" and "Associated Platforms" and anything else that might be relevant? I feel like I must be missing something here. In my searches I've seen a page listing Emulator Settings, and it mentions command line details for FBA: %name -r 640x480x32 Is that relevant for hosting Retroarch through Launchbox? Where would I put that? Did anything use/not use it?

SentaiBrad said So the command does need to be -L "cores (backslash) fba_libretro.dll". The forums don't like backslashes, so one needs to be there. Assuming that is correct, do the names in the Associated platform match the name of the System? In LaunchBox, on the left where your systems are listed, make sure the name matches in Associated Platform, they need to in order for the commands to be ran successfully. Are other cores with BIOS running properly? I am fairly certain the BIOS just need to be located with the games (at least as far as MAME is concerned) but RA confuses things a bit more in that regard and MAME is already super confusing. If all else fails, you can also try the stand alone emulator or MAME. Thanks for the response. Ah yes, the command you mentioned sounds accurate, including the core folder and the backslash. I did name the system "NeoGeo" since I'm 99% sure that is how the games heading is leading on the left side with the other platforms. I haven't messed much with other BIOS based cores, but I plan to. Maybe I'll jump over to experimenting with one of them. I'll keep those ideas in mind, thanks.

Hey folks, I'm new to Launchbox but have successfully gotten a nice collection of NES, Genesis, SNES and N64 games up and running since Saturday, and I'm really enjoying it. Now I've spent a while trying to get NeoGeo going, but I'm not having any success. I read that Final Burn Alpha was considered the best of the options between FBA and Mame, so I got the core through Retroarch like usual. I had to add NeoGeo since it wasn't listed as a system with default command line parameters, so I just used the typical formula -L "fba_libretro.dll" (forgive me if that's off, its from memory). I've tried a few different sets of ROMS, one of which should be considered current enough. Each time I've had an identical bios file (neogeo.zip) in the folder containing the roms themselves, as well as retroarch's system folder. Unfortunately, anytime I double click a Neogeo game in launchbox, like I would for any other system, nothing happens. The mouse has a "loading blue circle" for 1 or 2 seconds, and then nothing. Yesterday, I tried it direct through retroarch, I went to "load content" and picked a game and it loaded right up. What could be wrong with how Launchbox is interacting with FBA/Retroarch? I've searched everywhere and I'm at the end of my rope trying to figure it out on my own. Thanks!