Stoogie

You are correct, my apologies for being wrong. In the end it always comes around to romsets for this issue. The reason standalone application works(most roms depends on merged/unmerged/your romset) on an automated front(including on amberelec) is because it generates and uses a shared romset(shared meaning it can work with quite a lot of roms regardless), Retroarch doesn't however. So there is nothing wrong with Launchbox, Retroarch is a bit bad in dealing with romsets but the biggest issue is how Final Burn Neo is developed and created to work. FBneo is very user unfriendly and poorly designed and implemented and this is the biggest flawed emulator today out of all of them (arcade is the worst to get working), if only a proper programmer can program FBNeo to be user friendly with a self automated rom database scan and setup while taking in all variables (emulator version, romtype, rom game and prerequisites, all rebuilds, from a online database for example) (so basically like FBNeo Nightly which does most roms like what I just described but also with the ability to fix the remainder that are marked with a red circle of unavailability due to incorrect romset) That way more people can use it instead of just the "elitist trolls who "just" say to you to require a programming degree" /sarcasm Otherwise mostly all will give up. I have also read forum posts from the FBNeo devs which show elitism/immaturity, also the "THIS IS NOT A BUG" on the fbneo screen when romsets fail is also an indicator of this personality, not someone to be able to get along with, which is a detriment to emulator development as they refuse to fix the end user experience. Edit: I have seen hundreds of romset issue posts on lots of forums, theres quite a few here on launchbox too, it is a common complaint

I don't believe this is true, the way launchbox manage the rom database for arcade files associated with fbneo using retroarch loading in launchbox causes this problem and moving the rom files and readding the arcade/ NEO GEO AES / NEO GEO CD fbneo should fix it (that is if unticking unzipped doesn't work, in my case only worked for AES). All still run in standalone retroarch or standalone FB Neo Nightly for example. it is a problem with i Think nov 2022 update of launchbox.

Do not do this wrong it will crash your launchbox.(for me it was while downloading bezels) If you unselect the root tickbox then select the Arcade tick box and click ok it will instantly crash Launchbox (latest version) and when you try to reopen it the loading bar will go to 30% saying loading interface then will close and it repeats infinitely. How do I remove the tick I made and restore the original tick manually by editing files so I can launch launchbox again??????? Solved but with loss of time: Get a previous saved parents file that isnt changed(or replace whole data folder with this backup) (that you know by date and time) and copy over current one in this folder C:\Users\stoog\LaunchBox\Data C:\Users\stoog\LaunchBox\Backups\Automatic LaunchBox Startup Data Backup 2023-07-21 19-40-22.7z\Parents.xml Edit: after readding 1 of the missing ones the rest re-scanned in so thats a plus