libretro / libretro/RetroArch

MAME Content Fails to Load When Basename Matches Parent Directory Name

Open
#16,486 0 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

Description

I've got arcade ROMs sorted into their own folders and am running them through the regular MAME core. I was having problems getting Frogger to run and didn't understand why. I checked the logs and saw:

[libretro ERROR] Error: unknown option: frogger
[ERROR] [Content]: Failed to load content

I didn't know what to do, so I pressed on until I got to Breakers. I had the same problem. I then realized for both of those games, the ZIP's basename matched the parent directory's name. (frogger.zip was in a folder called Frogger and breakers.zip is in a folder called Breakers.) I appended (Parenthetical Added as RetroArch Workaround) to both folder names, reimported, and both now load fine.

Expected behavior

The games to load.

Actual behavior

The games don't load if the ZIP file's basename matches its parent folder's name.

Steps to reproduce the bug
  1. Put a ROM into a folder that has the same name as the game's basename.
  2. Import the game via manual import.
  3. Try to load the game.
Version/Commit

You can find this information under Information/System Information

  • RetroArch: 1.18.0
Environment information
  • OS: Arch Linux (KDE Plasma 6.0.4, Wayland session)
  • Official AppImage build

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

Reproduce the failure using manual import with a ZIP whose basename matches its parent directory, as described in the issue. Trace the manual-import and content-loading entry points to identify where the parent directory name is treated as an option; done means both Frogger- and Breakers-like layouts load successfully without renaming their folders.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.