I followed the tutorial video on importing FB Neo into Launchbox, but encountered an issue.
Certain ROMs were missing during the import process. They clearly exist in the Launchbox database, but it seems unable to recognize them.
For example, it fails to import ROM files like Akai Katana and Dodonpachi Saidaiojou, which are not part of the MAME romset. I tried rescan operations and re-importing, but they still won't add. Even when attempting to manually add the missing ROMs via drag-and-drop, the Import Wizard displays “0 games imported.”
I've tried changing all the options:
Unchecked “Search local metadata database”,
Checked “Force import duplicate games”,
Unchecked “Use MAME database”.
Even after trying every possible combination, nothing gets added.
This clearly seems like a functional issue, and I don't understand it. Where could the problem be?
Is there a specific file name structure required for import, and does it absolutely prohibit importing if the file name doesn't match?
If it worked properly, during the ROM import process from a folder, it should either import only those found in the database (omitting those without metadata), or import everything and display ROMs not in the database even if they lack metadata. At this point, with unintended, unknown missing files existing, I believe it has already lost its value as an emulator frontend.
However, seeing that it even refuses manual addition via drag-and-drop for individual missing files makes me suspect something is amiss, prompting this inquiry.
Is this actually the intended normal operation as designed by the developer? Or am I completely misunderstanding how it's supposed to work?
I recently reinstalled Launchbox entirely, using both the official build and updating to the beta build.
If I'm mistaken or there's a better way, please let me know.