|
> > Add this to your engine.cfg and you got internal M1 support (well...at least
> for
> > the latest M1 version)
> >
> > engine (
> > name M1
> > cachefile _m1dat
> > command -d
> > )
> >
> >
> > Roman Scherzer
> > ClrMamePro
>
> This is sweet! Will the new engine.cfg with M1 included be part of future
> ClrMamePro releases or do we need to make sure we don't overwrite our engine.cfg
> each time?
>
> Cheers,
> Tim
>
The M1 engine entry will be official in the next cmpro release. When using ClrMamePro's auto-update function, you will see a warning about overwriting your engine.cfg. You have to say allow that once then. Well....of course that depends...if you've already made changes for other stuff (like adding more mame build cachefiles etc...) you may won't overwrite it...but then you already know that overwriting prompt.
Roman Scherzer
ClrMamePro
|
