Open HTV04 opened 10 months ago
I found this issue independently because two of them are ROM hash duplicates instead of hashes of bad dumps:
kingkong1
(King Kong - The Official Game of the Movie (Europe) (En,Sv,No,Da,Fi)
)
kingkong
dogz2u1
(Dogz 2 (USA, rev. 1)
)
dogz2u
@HTV04 Hi, I was wondering how you got the save types? I'm interested in solving this issue, and I've been able to create my own list of hashes that need to be updated that largely matches your list, but No-Intro doesn't seem to consistently provide save type information.
If you have any related code from your GBA save-type database generator that could be referenced, that might also be helpful.
Hi; apologies for not using the bug report template. Since this isn't an issue with MAME itself, many of the fields didn't really apply.
Some time ago, I worked on a GBA save-type database generator using the entries from MAME's
gba.xml
file, alongside the No-Intro database for some additional info. However, I noticed that a few of the entries seemed to be either inaccurate or missing when comparing them with the No-Intro database (especially the notoriously unverified Classic NES dumps).It turns out that many of the inconsistencies I found were because the entries in
gba.xml
are actually using the hashes of known bad dumps. Here's an example; the trusted dump is above, while the bad (overdumped) hash is below:Hopefully, these entries can be of use and implemented into
gba.xml
, I'd love to be able to get rid of these overrides. Please let me know if I messed up anything here or if any of this is outdated.