Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[stealth318]

Not sure if this is a config issue or not.  Whenever I update DAT files (single or multiple), the version column of that partciular DAT file(s) will reset to "-/-" instead of the actual version number, e.g. 20200205-043446.  Even after updating the DAT successfully and performing a scan, the version remains as "-/-".  This becomes a bit of an issue when checking for DAT updates, since it'll always show an update is available for DAT files having version "-/-", even if it's not the case.

The workaround is to re-add one of the DAT files with version "-/-".  It'll prompt that the DAT file already exist and once I choose replace, it'll update every DAT having version "-/-" with the correct value.

Any ideas what's going on?

Currently running the latest clrmamepro build and don't recall encountering this in any previous versions.  This issue happens with No intro and MAMEUI DATs (only ones I'm using).  Thanks!

[Roman]

Hmm...interesting...actually hitting "refresh list" should redisplay it correctly, right?

Actually I think I found it already.....it's an old problem which was simply hidden in older versions since they always ran a "refresh list" internally. With the latest version, this is only done when it needs to be done and so that old version blanking is visible.

For now I guess a "refresh list" click can be used as a workaround....Next version will have it fixed

[stealth318]

Good to know, thanks Roman!

Evidently I couldn't test after your original response since none of my DAT files had updates available.

Looking forward to the next update!

[Roman]

The problem is not based in updating but the initial read. It prefers a "build" string as version in the datfile (which I guess is only available in a MAME datfile). The old automatic refresh read the correct information from the datfile header afterwards and the correct version was shown and saved. This automatic refresh is not triggered now and the blank "build" information is used.

So the problem also appears if you add a new datfile and create a new profile for it. Adding shows the correct version, after the initial profile save it's gone...and refresh shows it again ;-)

[Roman]

new nightly build....with the version thingie (hopefully) fixed

[stealth318]

Awesome!  Knowing about the refresh button is a great help already, thanks again.