lr-fbneo Romset validation with clrmamepro

thedan

Hello,

First I will try my best to write English, it's not my mother tongue.
I have the full FB Neo v0.2.97.44 Romset which I validated as non-merged with clrmamepro (with the provided DAT).
But when I scan with the DAT from retropie-dat-master there are errors (non fixable) all over the place.

As I understood the FB Neo Romset is constantly changing but the version stays the same 0.2.97.44.
For example a valid 0.2.97.44 Romset from 9 months ago is different from a valid 0.2.97.44 Romset today. Am I correct?

So it can be that I have the wrong 0.2.97.44 Romset for retropie?
How to find the correct one if all the versions are the same but different?

I also tried to use clrmamepro with a valid Mame Romset as source to fix the errors, but there is the same issue, as I don't know what exact version I am with my FB Neo 0.2.94.44 Romset how can I know which Mame Romset to use as source?

barbudreadmon

@thedan said in lr-fbneo Romset validation with clrmamepro:

For example a valid 0.2.97.44 Romset from 9 months ago is different from a valid 0.2.97.44 Romset today. Am I correct?

Mostly, actually we changed version number 6 months ago, current is 1.0.0.01.

@thedan said in lr-fbneo Romset validation with clrmamepro:

how can I know which Mame Romset to use as source?

We stay in sync with MAME, meaning if you update FBNeo from source today, it should mostly be in sync with MAME 0.229.

thedan

My goal is to validate my actual FB Neo 0.2.97.44 Romset towards retropie so I use the DAT from retropie-dat-master.

The DAT from retropie-dat-master is for FB Neo 0.2.97.44 and I have a valid FB Neo 0.2.97.44 Romset so I loaded it into a new Profile in clrmamepro and done a scan here are the results:

Missing
·Sets 3/5974
·ROMs 438/109336
·CHDs -/0
·Samples -/1333
·Bytes 180mb/56gb

Now which Romset do I need to fill the missing roms/sets?

barbudreadmon

@thedan said in lr-fbneo Romset validation with clrmamepro:

Now which Romset do I need to fill the missing roms/sets?

No idea, imho those dat files from retropie-dat-master are pointless since they have no real context. Do they match the software versions you have installed ? In the case of FBNeo there is a 99.999999999999% probability it doesn't. Romset must match emulator version, romset must not match some random dat file picked on internet.

thedan

Here is the header of the DAT file i'm using I think this is an correct one. It was provided with the romset I downloaded, and a scan with clrmamepro is 100% valid.

<name>FinalBurn Neo - Arcade Games</name>
	<description>FinalBurn Neo v0.2.97.44 Arcade Games</description>
	<category>Standard DatFile</category>
	<version>0.2.97.44</version>
	<author>FinalBurn Neo</author>
	<homepage>https://neo-source.com/</homepage>
	<url>https://neo-source.com/</url>
	<clrmamepro forcenodump="ignore"/>
</header>

So then I will stick with this and discard the dat from retropie, thank you for your answer.

barbudreadmon

@thedan said in lr-fbneo Romset validation with clrmamepro:

Here is the header of the DAT file i'm using I think this is an correct one.

Yeah, and that's the problem, since hundreds of dat files with different content had the same header over the course of 2 years, with matching MAME versions from 0.210 to 0.226. And there is a 99.99999999999% probability that dat file you are using isn't matching the FBNeo version you have installed.

If you tell me what commit of FBNeo you are using (bottom left of retroarch menu, should be right after version), i can give you the right dat file for it, but tbh i would just recommend to update FBNeo from sources and pick the latest dat file from https://github.com/libretro/FBNeo/tree/master/dats at the same time.

thedan

@barbudreadmon said in lr-fbneo Romset validation with clrmamepro:

i would just recommend to update FBNeo from sources and pick the latest dat file from https://github.com/libretro/FBNeo/tree/master/dats at the same time.

This means I could use the Romset FBNeo 1.0.0.01 with retropie?
I already tried what you said on your first post in this thread Goodbye fbalpha, welcome fbneo I took a valid Mame 0.229 Romset to update my FBNeo Romset with the latest DAT from github, but there are even more errors.
Can it be that the 0.2.97.44 Romset I have is an old one and that I need the Roms from other Romsets 0.210 to 0.226 too ?
It would be probably easier to find one of the latest FB Neo Romset then.

barbudreadmon

@thedan said in lr-fbneo Romset validation with clrmamepro:

This means I could use the Romset FBNeo 1.0.0.01 with retropie?

Of course you can.

@thedan said in lr-fbneo Romset validation with clrmamepro:

Can it be that the 0.2.97.44 Romset I have is an old one

Of course it is an old one, 0.2.97.44 was the FBNeo version from may 2019 to october 2020, your set could be from any date between those 2.

@thedan said in lr-fbneo Romset validation with clrmamepro:

It would be probably easier to find one of the latest FB Neo Romset then.

Yeah, it'll be easier to find a more recent one, but again keep it mind there are romset changes (redump or additions) several times a week. So whatever romset you manage to find, don't assume it'll be an exact match of current version, just over the course of the last 2 weeks the arcade dat file was updated 6 times, because of 2 new supported systems (Jaleco MegaSystem32 and Namco NA1/2) and some syncing with recent (re)dumps.

thedan

OK I managed to find a 1.0.0 FB Neo romset, updated FB Neo from source in retropie. As you said my romset is not 100% exact match with the current DAT from github but a lot of the missing or incorrect roms are Hacks, or homebrews etc. I don't really care about them. Works very well for now :)