LordShadowen

Thanks for tip, but I don't think that's it. That specific rom has not been imported yet, so how could it be a duplicate? A duplicate of what? Also, just for testing, I checked that box "Force duplicates" and it still doesn't import it. I don't even have to finish the process, I can see it's not on the list at the last step of the wizard. Any other ideas?

Why certain roms don't import and how do we know which ones were skipped? Here's a specific example - a folder contains a complete set of 56 roms for Supermodel (Sega Model 3). The zips all follow MAME naming conventions. The import is done for the Supermodel 3 platform, and the box "Force using MAME metadata" is checked. The import finishes, and it says "55 games imported". It does not say it skipped 1 file. The same thing happens even if select all files from the folder or even drag and drop all 56 files. I only know a file was a skipped because I knew ahead of time they were supposed to be 56. I did some manual checking and it turns out that this particular ROM has been renamed in MAME , but Supermodel is still using the old name, so I guess it's not in the database? But why it is skipped? Shouldn't it just be imported with no info so that we can manually edit it? Also, in this particular case, I know which one was missing because they were only a few, but let's say there were thousands of files... it would be impossible to easily know which ones were skipped. Is there any way that LB can provide that information? During import or after? Audit does not help, because it only lists the imported files.... Finally, I noticed something really odd - if I try to import all the files again (wizard or drag and drop) that file is always skipped. But, if I drag and drop that ONE file, and only that file alone, then it will import it. Of course, without any metadata, but it will work. Why is this? Very confused...

Ah, got it. So basically, LB has built-in logic that says "treat Sega Model 2 platform roms as MAME roms" no matter what (regardless of the checkbox). It's only by creating a custom platform that you can get away from that. That's different from what Neil was saying... I wonder if it's a bug or by design. If intentional, not sure if that's a good idea or not, but what's interesting is that there is never a scenario where the entries from the Files.xml are ever used then.... it's either MAME or treated as "unknown" and the names are just the file names (without prefix).

Ah, that explains a lot, thank you. So, as long as they are treated as MAME roms, everything that is happening makes sense now. However, the last part is still unclear: I can't replicate this - I'm using the "Sega Model 2" platform, not checking the MAME box, not using MAME as the emulator and the import list always shows the exact same thing. What I expected is that by doing what you say (and that I've tried), LB would not associate these files to MAME in any way, and use the Files.xml descriptions instead. It looks like there is some sort of "assumed" MAME connection no matter what I try... are you able to get the names out of Files.xml? e.g. "Daytona USA: GTX2004" on daytonagtx when you do it?

Thanks, but unfortunately got exactly the same results, made no difference. I've tried with all the options to not skip anything, and even force duplicates (just in case), but always end up with the same 7 (still no '93 version), with the same names (just like in my first post) In fact, it looks like LB was already somehow handling it as MAME shortnames, otherwise it wouldn't have found anything at all right? There must something else going on. Any other ideas?

Total noob here, just starting - sorry if this is explained somewhere else. So, to start small, I tried importing a complete set of Sega Model 2 roms, using the Sega Model 2 platform and the Model 2 Emulator 1.1a. Mostly it works fine, but there is some weirdness I don't understand. Let's take the example of Daytona - there are 8 "versions" of Daytona listed in the emulator: I have each of these 8 romsets as zip files (daytona.zip, dayton93.zip, etc...). They all launch correctly from the emulator directly. When I import this folder in LB, this is what it finds: You'll notice that it finds 6 "Daytona USA" and 1 "Daytona USA Special Edition" - so 7 in total. It does not find the Daytona '93 Edition at all. I figured that there must be an issue matching the names with the database. I looked in the file "Files.xml" (btw, is this the right place to look?), and it's even stranger because I found this: <File> <Platform>Sega Model 2</Platform> <FileName>dayton93</FileName> <GameName>Daytona USA Deluxe '93</GameName> </File> <File> <Platform>Sega Model 2</Platform> <FileName>daytona</FileName> <GameName>Daytona USA</GameName> </File> <File> <Platform>Sega Model 2</Platform> <FileName>daytonagtx</FileName> <GameName>Daytona USA: GTX2004</GameName> </File> <File> <Platform>Sega Model 2</Platform> <FileName>daytonam</FileName> <GameName>Daytona USA: To The Maxx</GameName> </File> <File> <Platform>Sega Model 2</Platform> <FileName>daytonas</FileName> <GameName>Daytona USA (Saturn Ads)</GameName> </File> <File> <Platform>Sega Model 2</Platform> <FileName>daytonat</FileName> <GameName>Daytona USA Turbo</GameName> </File> The file has 6 entries (not 7 or 8). It does contain the 93 edition, and it does not contain any "Special Edition". Also, the names for each version are distinct (and even roughly match their Emulator names), and not simply "Daytona USA" like the import dialog shows. I'm very, very confused ? Anybody can explain what's happening? Am I misunderstanding the whole thing?