Welcome to Emulationworld

Forum Index | FAQ | New User | Login | Search

*View All ThreadsShow in Flat Mode*


SubjectRe: clrmamepro 3.84b released Reply to this message
Posted byRoman
Posted on03/03/06 03:07 AM



Could be caused by several stuff....

1)
These are sets with merging-between-systems. They always existed but I might have changed the default answer for it when adding the new yes/no/yestoall windows. You were always able to set the value which you prefer when you kept 'datfile errors' -> show all. You can also set 'Pro_ForbidSystemMerging' to on/off in cmpro.ini to select the default value.

2) if you enabled the usage of merge tags (parse merge tags) it could be a normal behaviour. I told the people before...merge tags in MAME are unreliable 8)

Although nothing of that actually changed from 384a to 384b. I guess it's 1) and you haven't cleaned the cache from 384 to 384a, so the data wasn't newly received, so it still used the old setting for that.

What you currently can do: Add the upper mentioned ini line to cmpro.ini (set it to "off" I guess), clean the cache and reget the data from a mame executable.



Roman Scherzer


-
Entire Thread
Subject  Posted byPosted On
*clrmamepro 3.84b released  Roman03/02/06 01:53 PM
.*Re: clrmamepro 3.84b released  dbaugh03/02/06 10:02 PM
.*Re: clrmamepro 3.84b released  dbaugh03/02/06 09:32 PM
...Re: clrmamepro 3.84b released  Roman03/03/06 03:07 AM
...*Re: clrmamepro 3.84b released  Roman03/03/06 05:42 AM
....*Re: clrmamepro 3.84b released  Roman03/03/06 12:05 PM