Roms unsync with latest mame (0.226)

Question

Roms unsync with latest mame (0.226)

LodanZark opened this issue 4 years ago · 6 comments

The "epr-10381a.132" got renamed to "epr-10381b.132" and the "epr-10381.132" (outrundx) no longer exists, due having the same hashes as "epr-10381b.132" which it's located in parent ROM.

Answer 1 · 2021-03-02T22:49:07.000Z

I will look into this.

Answer 2 · 2021-03-03T17:46:04.000Z

The last changes can be found here: https://github.com/mamedev/mame/blob/master/src/mame/drivers/segaorun.cpp

Answer 3 · 2021-03-03T18:33:46.000Z

Thanks. I'm ideally going to load everything by CRC scanning the directory, rather than relying on file names.
MAME changes these all the time and it will just cause confusion.
I'm aiming to work on this in the next few days :)

Answer 4 · 2021-03-03T20:23:33.000Z

If you're familiar to using rom managers tools like clrmamepro, maybe this dat\xml file will be useful to you:
MAME 0.229 ROMs (split).zip

Answer 5 · 2021-03-03T21:37:49.000Z

Cool. Same ROMs, just seems the MAME devs rename them every other week.

Once I switch to CRC32 based loading it won't matter what the filenames are.

Answer 6 · 2021-03-04T15:26:45.000Z

Checked in CRC32 based file loading. Searches for CRC32 value, not the file name itself.