libretro / libretro/libretro-database

Virtual Console entries no longer found

Open
#598 22 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.4k
Forks
877
Avg merge
3d 1h
Merged PRs (30d)
24

Description

I noticed with the latest version of the database that a bunch of Virtual Console entries weren't getting recognized by RetroArch's scanner - looking at the current revision I'm not entirely sure where these would be located; I thought that it might be this issue I found when building the Wii database...

/home/steam/libretro-super/retroarch/media/libretrodb/dat/Nintendo - Wii.dat:66349:6: fatal error: Unexpected '(' instead of key

I'm assuming this is a red herring though, as I'm not using the full WADs, just the extracted ROM with sound restored (so previously the files were recognized as "(VC) Sound Restored"). Files that are the same as the original SNES data are fine (Star Fox 1/2, Yoshi's Island). The last time this worked was with the SteamOS-Tools version, v1.6.1 with a couple patches for SDL_GameController support:

https://github.com/mdeguzis/SteamOS-Tools

Is there a separate database I should be looking at, or is there a bug I should track down?

Contributor guide

No contributing guide indexed for this repository

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 Nintendo - Wii.dat parse error at line 66349 and the RetroArch scanner behavior for extracted Virtual Console ROMs. Compare the affected entries with the working SNES entries and the prior SteamOS-Tools v1.6.1 behavior; done means identifying whether the database or scanner prevents these entries from being recognized.

Written by the indexing model from the issue text.

Assessment

Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.