... first of all, after you deleted the .db1 file, did AF recerate it, and did you see one for playstation and one for playstation-hw?
AF recreates the db1 file for Playstation only.
Ok, I was able to replicate the issue, and it is related to the way AF creates its database, maybe I'll find a fix in the future, but right now I have a workaround: let's say you want to use a romlist for playstation games, and you have two emulators you want to use, let's call them PSX-EMU1 and PSX-EMU2, ok? You need your setup like this:
Emulator folder:
Here you must have the two emulator config files, let's call them PSX-EMU1.cfg and PSX-EMU2.cfg, pointing to the same rom folder.
Romlist folder:
Here you need THREE romlists:
- PSX-EMU1.txt with all the games, all with PSX-EMU1 set as emulator
- PSX-EMU2.txt with the same games, but all set to PSX-EMU2 as emulator
- PSX.txt this is the "merged" romlist where you set the emulators to your liking, some with PSX-EMU1, some with PSX-EMU2
At this point if your Display points to PSX.txt as romlist, everything should work fine, scraping included.
Basically, for AF to work correctly, there should always be a romlist with the same name as the emilator, where all the games have the same emulator. So if you want to create a "mixed" romlist you'll need first to create romlists with each single emulator pointing to the same roms. Then you can create the mixed romlist which must have a name that's different from the emulator name.
Let me know if this fixes your issue, whie I try to implement a real solution for mixed emulator romlists that have the same name as an emulator
