1
clrmame Discussion / Re: Auto Assign only setting 3 [Soft] systems to the \software directory
« on: Yesterday at 06:26 »
Auto assign is a pretty easy best-count-wins and it works as follows:
For assigning standard/mechanical/decives/bios and software lists folders it runs through all active rompaths (not subpaths).
Then it counts +1 for per found file/folder for the belonging type. The type which gets the highest value gets this rompath assigned, otherwise the 1st rompath is used.
So you see, you need correctly named files in the paths to actually be able to assign a path, otherwise you all end up with the first rompath.
E.g. you have a rompath e:\roms\a2600 and got 99 valid atari 2600 sets in there and 50 sets of let's say C64, then that rompath gets a count of 99 for Atari 2600 (and most likely much less than the Atari 2600 count for other rompaths) and so the Atari 2600 software list gets assigned to that rompath.
The auto assign might be improved by also checking the rompath name, so e.g. an empty nes folder can be assigned to the nes software lists. That might get in in the near future....but generally the combined mode is pretty dead.
So....the combined mode is a pain to setup since auto assign would only work if you already have sets in all of your paths. And all paths have to be 1) rompaths and b) distinct (besides the 'normal' MAME ones BIOS/STANDARD/MECHANICAL/DEVICES)). Works pretty well if your collection is near perfect, but otherwise you most likely need to assign some or more paths manually.
You can't have "M:/Mame/software" as a rompath. Software lists need to be in distinct paths (which I assume are the subpaths of M:/Mame/software), so you need to add those as rompaths and not their parent paths. You can simply use drag'n drop in the settings folder to add them.
Overall, it's way more easy to use one-profile-per-software lists and run through the data separately. Why?
a) you got the batcher to scan only changed software lists
b) the batcher also allows you to auto-create and assign rompaths for you (no need to setup some hundred paths)
c) the scan results output is way more readable
d) some software lists are not exported by mame via -listsoftware while the hash files have them
e) no problems with identical sets (there are identical sets in MAME which repeat themselves in some software lists)
f) faster lookups
(batcher = select more than one profile in the profiler and hit load, then the batcher with all its options appear)
For assigning standard/mechanical/decives/bios and software lists folders it runs through all active rompaths (not subpaths).
Then it counts +1 for per found file/folder for the belonging type. The type which gets the highest value gets this rompath assigned, otherwise the 1st rompath is used.
So you see, you need correctly named files in the paths to actually be able to assign a path, otherwise you all end up with the first rompath.
E.g. you have a rompath e:\roms\a2600 and got 99 valid atari 2600 sets in there and 50 sets of let's say C64, then that rompath gets a count of 99 for Atari 2600 (and most likely much less than the Atari 2600 count for other rompaths) and so the Atari 2600 software list gets assigned to that rompath.
The auto assign might be improved by also checking the rompath name, so e.g. an empty nes folder can be assigned to the nes software lists. That might get in in the near future....but generally the combined mode is pretty dead.
So....the combined mode is a pain to setup since auto assign would only work if you already have sets in all of your paths. And all paths have to be 1) rompaths and b) distinct (besides the 'normal' MAME ones BIOS/STANDARD/MECHANICAL/DEVICES)). Works pretty well if your collection is near perfect, but otherwise you most likely need to assign some or more paths manually.
You can't have "M:/Mame/software" as a rompath. Software lists need to be in distinct paths (which I assume are the subpaths of M:/Mame/software), so you need to add those as rompaths and not their parent paths. You can simply use drag'n drop in the settings folder to add them.
Overall, it's way more easy to use one-profile-per-software lists and run through the data separately. Why?
a) you got the batcher to scan only changed software lists
b) the batcher also allows you to auto-create and assign rompaths for you (no need to setup some hundred paths)
c) the scan results output is way more readable
d) some software lists are not exported by mame via -listsoftware while the hash files have them
e) no problems with identical sets (there are identical sets in MAME which repeat themselves in some software lists)
f) faster lookups
(batcher = select more than one profile in the profiler and hit load, then the batcher with all its options appear)
...and noone else reported such a thing yet (and removing files it one of the most common things)...so I somehow have your taken-over-hd in mind...but currently no idea what's causing a crash.
.