Lordmonkus Posted January 26, 2018 Share Posted January 26, 2018 Ok, NeoGeo bios only need to be in the same folder as the roms. It's one of the few bios files that doesn't need to be in the \system folder. I'm just trying to think of anything at this point that would cause some sort of issue. Quote Link to comment Share on other sites More sharing options...
Nour T. Posted January 27, 2018 Author Share Posted January 27, 2018 14 hours ago, Charco said: Are you sure it's the same FBA core in your associated platforms as what you're using in RA? There are 3 options that will run Neo Geo games, each possibly supporting different rom sets. Yes, tried the same core on the extracted retroarch and installed retroarch. The core I'm using is fbalpha. Quote Link to comment Share on other sites More sharing options...
Lordmonkus Posted January 27, 2018 Share Posted January 27, 2018 What is the path that your Neo Geo games are located ? I have seen instances where if the total command line length or if the command line had some weird characters in it that caused issues. Quote Link to comment Share on other sites More sharing options...
Nour T. Posted January 28, 2018 Author Share Posted January 28, 2018 Okay, I have finally solved the problem, and I'm going to edit the thread so that it has the solution for those who are struggling: This time, I have put the downloaded roms (not from Launchbox) into a seperate folder and it actually works, finally. It seems that copying the files to Launchbox/Games really does weird things to the roms. Thank you all for help. ^^ Quote Link to comment Share on other sites More sharing options...
Lordmonkus Posted January 28, 2018 Share Posted January 28, 2018 Now it makes sense, you were copying your roms over to the LB rom folder and there was no bios being copied over so FBA was not seeing your bios. Edit: If you want to have your rom files in the LB\roms folder you would need to copy over the neogeo.zip bios into that folder manually. 1 Quote Link to comment Share on other sites More sharing options...
Retro808 Posted January 28, 2018 Share Posted January 28, 2018 33 minutes ago, Lordmonkus said: Now it makes sense, you were copying your roms over to the LB rom folder and there was no bios being copied over so FBA was not seeing your bios. Edit: If you want to have your rom files in the LB\roms folder you would need to copy over the neogeo.zip bios into that folder manually. And there it is. You even asked about the bios early on. A good pro tip going forward on a reason why one should not use the move option during importer. @Nour T. glad you finally got sorted. Quote Link to comment Share on other sites More sharing options...
neil9000 Posted January 28, 2018 Share Posted January 28, 2018 lol, 2 pages to find its a simple bios issue. Well at least its all working for you now. Quote Link to comment Share on other sites More sharing options...
Lordmonkus Posted January 28, 2018 Share Posted January 28, 2018 1 hour ago, Retro808 said: You even asked about the bios early on. Yeah I asked about bios but it completely slipped my mind to think of maybe he was copying his roms during the import. Quote Link to comment Share on other sites More sharing options...
machjas Posted April 24, 2021 Share Posted April 24, 2021 Hi all! I know this is an old thread, but I read through it today as I was having a very similar issue to the OP using RetroArch/FBNeo with Launchbox v11.11 - I tried switching between the universal and the original neogeo BIOS, tried putting neogeo.zip in the rom folder, the RetroArch system folder, etc.. I would go into retroarch directly, load the core and check info, it could see thee BIOS file, so I'd do Load Content, browse to a game directly and it would work fine, just not when I go through LaunchBox. My solution ended up being under Manage Emulators > RetroArch, and UNCHECKING the "Extract ROM Archives Before Running" and it works perfectly through LaunchBox I just hope that, since that option is a universal RetroArch setting (I think?), that it doesn't break any of my other systems that might require that option. If this ends up being the case, is there a workaround, or do you think I would need to use a standalone FBNeo or a separate RetroArch instance solely for FBNeo so I can leave this unchecked? Quote Link to comment Share on other sites More sharing options...
Lamaman1971 Posted January 28, 2022 Share Posted January 28, 2022 I had this issue - and unchecking the extraction option fixed it for me too - not sure what the problem was there though. Quote Link to comment Share on other sites More sharing options...
neil9000 Posted January 28, 2022 Share Posted January 28, 2022 15 minutes ago, Lamaman1971 said: I had this issue - and unchecking the extraction option fixed it for me too - not sure what the problem was there though. Is cause arcade games should never be unzipped, mame or fba needs the zip file, not the contents of it. Quote Link to comment Share on other sites More sharing options...
Lamaman1971 Posted January 28, 2022 Share Posted January 28, 2022 My ROMS are zipped. Quote Link to comment Share on other sites More sharing options...
Atki2022 Posted August 18, 2022 Share Posted August 18, 2022 On 1/29/2022 at 2:32 AM, Lamaman1971 said: I had this issue - and unchecking the extraction option fixed it for me too - not sure what the problem was there though. On 4/25/2021 at 7:57 AM, machjas said: Hi all! I know this is an old thread, but I read through it today as I was having a very similar issue to the OP using RetroArch/FBNeo with Launchbox v11.11 - I tried switching between the universal and the original neogeo BIOS, tried putting neogeo.zip in the rom folder, the RetroArch system folder, etc.. I would go into retroarch directly, load the core and check info, it could see thee BIOS file, so I'd do Load Content, browse to a game directly and it would work fine, just not when I go through LaunchBox. My solution ended up being under Manage Emulators > RetroArch, and UNCHECKING the "Extract ROM Archives Before Running" and it works perfectly through LaunchBox I just hope that, since that option is a universal RetroArch setting (I think?), that it doesn't break any of my other systems that might require that option. If this ends up being the case, is there a workaround, or do you think I would need to use a standalone FBNeo or a separate RetroArch instance solely for FBNeo so I can leave this unchecked? Wow I was losing my mind trying to work out why this wouldn't launch and as with you both it was the same issue. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.