[3DS] Entire system crashes when launching a .cue or .chd file
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 am trying to play Vib Ribbon on my New Nintendo 3ds XL. When I load from a .bin file, the levels' songs don't play, because not all the tracks are being loaded, but the game itself works fine. To remedy this, everyone I've seen has recommended I use ISObuster to combine the 8 .bin tracks into one, and launch the game via the .cue file from retroarch. But when I do this, my entire system crashes, giving an arm11 error. The same thing happens when I use a .chd file, which was also recommended online. This also happens when I use the .cue file and all 8 .bin files (uncombined); launching anything but a .bin file causes a system crash. Unsure if it is a retroarch problem or a cfw problem.
Expected behavior
I expected the game to run.
Actual behavior
I have to force shutdown my entire DS.
Steps to reproduce the bug
- Vib Ribbon .bin files combined into one .bin file
- pcsx reARMed core being used
- I import content from my Games folder on my microSD card; the entire folder (which is just the vibribbon .cue and .bin, as well as a .chd file that gives the same results) is imported.
- the .cue file is ran
- the system goes completely dark and crashes.
Bisect Results
I can launch the game from a .bin file just fine, but it is incomplete. So this only happens when launching using a .cue or .chd.
Version/Commit
Latest version of RetroArch as of writing this, as I just downloaded everything today.
Environment information
- OS: I'm on a Windows 10 computer to manage these files, but the system I'm using is a New 3DS XL.
I turned on log reporting and replicated the issue but nothing got output to the /logs/ folder; perhaps because the system crashed before it could do that.
I have my crash log from Luma, but I can't seem to get it to output as anything readable, so I just have the .dmp file. If that'd be helpful, let me know.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the crash on a New Nintendo 3DS XL with the pcsx reARMed core using the reported .cue and .chd files, then inspect the available Luma crash dump because RetroArch produced no logs. Done means these disc-image formats launch without crashing the system and the game's tracks load correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- game-dev, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100