Hi,

Feature request Roman.... when I use huge DATs sometimes I only want to select a subset to audit, by using wildcards in the "Select Sets" box in the Settings menu. Thing is, every time I restart ClrMame or reload the DAT I need to re-enter this filter. Would it be possible to "remember" which of the sets have been selected from one session of the program to the next?

Hope you know what I'm trying to say :p

Thanks,
Mike

> Hi,
>
> Feature request Roman.... when I use huge DATs sometimes I only want to select a
> subset to audit, by using wildcards in the "Select Sets" box in the Settings
> menu. Thing is, every time I restart ClrMame or reload the DAT I need to
> re-enter this filter. Would it be possible to "remember" which of the sets have
> been selected from one session of the program to the next?
>
> Hope you know what I'm trying to say :p


I know what you mean ;) When new data is loaded (e.g. new MAME or datfile version is used), all set selections will be reset to 'all'.

Datfiles all share the same cachefile (see engine.cfg), so loading 2 different dats will always reset the set-selector data.
What you currently can do: add a new engine with a different cache entry to engine.cfg and use that for the datfile where you use only some sets....

I will make a note about your request, although it's not that simple, since if data did change (not only because the cache was updated), it doesn't necessarily mean that the old 'pacman' set is the same as the new 'pacman' set.


Roman Scherzer

> Datfiles all share the same cachefile (see engine.cfg), so loading 2 different
> dats will always reset the set-selector data.
> What you currently can do: add a new engine with a different cache entry to
> engine.cfg and use that for the datfile where you use only some sets....
>
> I will make a note about your request, although it's not that simple, since if
> data did change (not only because the cache was updated), it doesn't necessarily
> mean that the old 'pacman' set is the same as the new 'pacman' set.

Thanks for your reply Roman. So for now, which engine would it be best to use ie. which is the most "generic" one? And how do I link an engine with a DAT?
Sorry for sounding like a n00b :p

Thanks again!

> Thanks for your reply Roman. So for now, which engine would it be best to use
> ie. which is the most "generic" one? And how do I link an engine with a DAT?
> Sorry for sounding like a n00b :p


If you work with datfiles, copy/paste the datfile one:

engine (
name DATFILE
cachefile _datfdat
)

Add it with different Names and cachefile names (like DATFILE_1 _datfdat1 etc...)

In the profiler you click on a profile and at the bottom of the window you can change the used engine. Click on load (without reclicking somewhere else) and the profile is loaded with the new assigned engine...and that setting is saved). So for example you can use "datfile1" for your profile where you only selected some sets, while "datfile" belongs to the others. Since it uses a differnt cachefile, your setting selections will be remembered (until your datfile changes).


Roman Scherzer

> Add it with different Names and cachefile names (like DATFILE_1 _datfdat1
> etc...)
>
> In the profiler you click on a profile and at the bottom of the window you can
> change the used engine. Click on load (without reclicking somewhere else) and
> the profile is loaded with the new assigned engine...and that setting is saved).
> So for example you can use "datfile1" for your profile where you only selected
> some sets, while "datfile" belongs to the others. Since it uses a differnt
> cachefile, your setting selections will be remembered (until your datfile
> changes).

Fantastic! Now I get it. Thanks a lot Roman, appreciate your help!