libretro / libretro/RetroArch

PrBoom fails to start in RetroArch v1.11.0+ on a Nintendo 2DS XL

Open
#14,722 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

core bugs - not retroarch bugs core issue
Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Description

PrBoom fails to start when prboom.cfg file exists already on a Nintendo 2DS XL device. PrBoom works fine in RetroArch v1.10.3 version. It'll give a black screen when running in 1.11.0+. PrBoom core hasn't changed since 1.10.3, so I suspect it's a regression in the RetroArch backend.

Expected behavior

PrBoom loads.

Actual behavior

PrBoom fails to load and stuck on a black screen.

Steps to reproduce the bug
  1. Load Doom through PrBoom core.
  2. Start a game so that the prboom.cfg file is created.
  3. Quit the game and close RetroArch.
  4. Restart RetroArch.
  5. Load Doom again, this will now give a black screen.
  6. Deleting the prboom.cfg file in the cores folder will allow the game to start properly again.
Bisect Results

This works fine in RetroArch 1.10.3.

Version/Commit

You can find this information under Information/System Information

  • RetroArch: 1.11.0 and above.
Environment information
  • OS: Nintendo 2DS XL with 11.16 firmware

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 an existing prboom.cfg on a Nintendo 2DS XL, comparing RetroArch 1.10.3 with 1.11.0 and later versions. Start by bisecting the regression and tracing the RetroArch configuration-loading path involved when PrBoom starts. Done means PrBoom loads successfully with prboom.cfg already present, without requiring the file to be deleted.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.