Final Burn Neo > FBN Discussion

DAT File to use with libretro core

(1/3) > >>

TheDan:
I acquired the most recent update for the libretro fbNeo 1.0.0.03 core within RetroArch. Subsequently, I obtained the latest DAT file from this GitHub repository: https://github.com/libretro/FBNeo/tree/master/dats. I then proceeded to rebuild my romset using clrmamepro.

Despite having validated the games using the latest DAT, some of them fail to work with the fbNeo core. Hence, my inquiry is whether the current version of the FB Neo core in RetroArch aligns with the most recent DAT available on GitHub. Given that there is no indication of a specific commit information is provided, I am uncertain how to identify the correct DAT file to download from the GitHub repository. Could you please provide guidance on how to determine the appropriate DAT file for download?

barbudreadmon:

--- Quote from: TheDan on December 20, 2023, 05:37:54 AM ---Hence, my inquiry is whether the current version of the FB Neo core in RetroArch aligns with the most recent DAT available on GitHub.

--- End quote ---

The dat file aligns with the latest commit available in the very same github repository you downloaded it from, meaning the latest version.
The logical conclusion would be that, for some reason (which i could maybe guess if you gave information about your setup), you are not using the current version of FBNeo.
Also, you can check which version of this core you are using by looking into the bottom left corner of retroarch menu, you should see "FinalBurn Neo (v1.0.0.03) 3b19f28a8" if you are using latest version, the letters at the end being part of the versioning (commit hash).

TheDan:

--- Quote ---Also, you can check which version of this core you are using by looking into the bottom left corner of retroarch menu, you should see "FinalBurn Neo (v1.0.0.03) 3b19f28a8"
--- End quote ---

It appears that the issue lies with RetroArch as it provides conflicting information. In the updater menu, it displays "FinalBurn Neo (v1.0.0.03)" without the hash. However, upon loading the core, it shows "FinalBurn Neo (v1.0.0.01) 4f493a1." Strangely, there were instances where it showed "(v1.0.0.03)" without the hash after loading the core, but this seems inconsistent.

Despite attempting to resolve the problem by deleting and reinstalling the core multiple times, it persists and appears to be buggy in some way.

I'm using RetroArch version 1.10.3, and I'm wondering if this is a known issue within RetroArch. The situation is further complicated by the fact that I'm using a handheld device, limiting my control over RetroArch.

barbudreadmon:

--- Quote from: TheDan on December 20, 2023, 07:35:53 AM ---4f493a1

--- End quote ---

You are using a 3 years old version, you can download the corresponding dat files for that version at https://github.com/libretro/FBNeo/tree/4f493a1d394282d4758e78d416324142818e19df/dats

I'd recommend figuring out why you are stuck with old retroarch and cores though, maybe you can find help on their forum or reddit. Note that we won't be able to provide further support if you use an outdated version of our core.


--- Quote from: TheDan on December 20, 2023, 07:35:53 AM ---The situation is further complicated by the fact that I'm using a handheld device, limiting my control over RetroArch.

--- End quote ---

I'm not entirely sure what you mean by that, you should share more details.

TheDan:
Yes thanks for the answer, i will continue to search on the Retroarch/Handheld side for this issue.


--- Quote ---The situation is further complicated by the fact that I'm using a handheld device, limiting my control over RetroArch.
--- End quote ---

I'm using the Anbernic RG35XX-Plus, a handheld device that comes with RetroArch preinstalled. Therefore,  I think my RetroArch configuration is not in its default state and already customized for the device; for instance, the Online Updater was disabled by default, perhaps due to concerns about its proper functionality.

Navigation

[0] Message Index

[#] Next page