clrmamepro [English] > clrmame Discussion

mame merged sets not scanning correctly?

<< < (2/6) > >>

Roman:
Check: Profiler->Options-> Naming Pattern should be "%f\%1" (which is default by the way)

Ensure that Settings->Full Merge Mode -> "Hash Collision Name"  is ticked, leave cmpro, start it, click on Profiler "Clear Cache" and reload the profile....

Pandor:
followed your suggestions, but still same result.

Roman:
Hmm....nasty....try this: in Scanner, click on "split sets" and then again on "merged sets". Open SetInformation (bottom left button in scan results window), enter "m4pitfala" in prefered at top to jump to the pitfall set (remember your first screenshot...there you have the same.....), and click on a subitem like Pitfall (Empire) (MPU4, set 3)....on the right side you should see then "m4pitfalb\pf2_0.bin" listed (*with* subfolder).

Is this the case? If no, hmm....maybe you should remove the profile and create a new one...If yes, then please do a new scan and show one single error message again

Pandor:
CMP does (now) show the subfolder in front of the rom in the SetInformation, and pitfall seems okay now.

But now i'm left with a large list of "missing but fixable"

Seems like pit fighter rev4 want the include roms that are from pit fighter rev3 (and are present).
I don't believe this should be by design for a merged romset, as the proceeding revision already has the correct files.

settings and profile are correct (I believe):


Ater all this,
I tried starting over from a freshly unzipped CMP, reloading mame.exe,.... nothing seems to do the trick.

Roman:
First of all, it's all about interpretation. MAME itself doesn't care about filenames, it simply takes an archive and looks by hash for the needed file. So to make it playable, you don't need an audit tool....simply put all garbage into a file and you're done :)

The interpretation for parent/clone relationships within cmpro is that clones can share a file with their parent but not with other clones.
The relationship is either based on identical names or on the "merge" atttribute in the datfile/-listxmloutput. By default, cmpro uses the merge attribute information (See profiler options "parse rom merge tags").

So yes...if you have Parent P with rom p1, Clone C1 with rom p1, c1 and Clone C2 with rom p1, c1, c2 and clone C3 with rom c3 only, you will end up in a merged set with:

p1
C1/c1
C2/c1 + C2/c2
C3/c3

That's the way it is, it won't change and hasn't changed since 1997 now..... :-)

There is no information that a version 3 is older or newer than a version 4 of a set. The relationship is defined in the datfile....if version is was designed to be the parent, version 4 and 3 could be clones...maybe a dev decides later on that 4 becomes parent....there is no real rule on that....one day it was "the most common version", then "the us or europe version", then the initial version .....there were lots of plans to set a rule on it...but actually I don't see one.


By the way, if they are identical (hash and name) you can get rid of the few extra bytes by simply NOT using subfolders for clones...then you only get them 1 time in the archive.....

Navigation

[0] Message Index

[#] Next page

[*] Previous page