Give the user the choice to import mame sets based on local dat file

Issue #5722 new
famigami created an issue

I found myself unable to import Mame 0.225 roms because Launchbox isn’t recognizing the new games. Rather than have the user rely on the launchbox DB hash file, why not give the user the choice to use their local dat file? That way if the user is updating more frequently than Launchbox, the user can make that choice. As is, the user can only import the roms without selecting the mame emulator which imports the games using the rom names which is useless.

Also, if the user wishes to import “non working” (they aren’t always actually non-working, many do!) they should be allowed to import EVERYTHING, using the name in the mame dat file, even BIOSes (many older systems have games in the bios file).

It’s nice to have a reliable server side dat file to check against for the average user, but I’m not convinced launchbox should bear the brunt of responsibility for that, especially since it isn’t updated for every version (nor should it necessarily be), there is no way of knowing what version is currently “supported”, and users shouldn’t have to wait, then update through several iterations of mame at once when launchbox does increase it’s “supported” version.

Comments (2)

  1. Log in to comment