libretro / libretro/RetroArch

FBNeo: some roms not in playlist after scan with database match

Open
#11,133 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

I followed this https://docs.libretro.com/guides/arcade-getting-started/ guid to build (check&fix) the FBNeo 0.2.97.44 romset (only a small portion) in the Full Non-merged way (and then TorrentZip), and after a database-matched scan, the playlist for FBNeo populated. But I noted some roms were not in the playlist, but they are playable by loading content with FBNeo core.

For the ones not in playlist, they are listed in the FinalBurn Neo (ClrMame Pro XML, Arcade only).dat, and the crc checksums for all files in the zip match the desc in the xml. But the scan failed for them.
BTW I saw there might be a MD5 checksum in the FBNeo - Arcade Games.rdb, Does the scanning process check the md5 of the zip first?

OS: Android 10
RA: 1.8.9 arm64 Google Play
Core: FBNeo v0.2.97.44 039fcad
I can name one or two roms if you want confirm & test, i.e. raiden, raiden2.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the arcade getting-started guide and compare the FinalBurn Neo (ClrMame Pro XML, Arcade only).dat entries and FBNeo - Arcade Games.rdb data for the named raiden and raiden2 ROMs. Reproduce the database-matched scan on the reported Android 10 setup, then determine why checksum-matching archives are omitted and document whether the zip MD5 is checked; done means the cause and affected scan behavior are confirmed.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
database
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.