Can’t Get Past Boot Screen In A Few Games

[ThisByzantineConduit]

What version of melonDS DS are you using?

1.1.1

Does the problem happen in standalone melonDS?

No, the games boot just fine in both the standalone release and the legacy MelonDS core.

What happened?

Games that boot just fine in the MelonDS legacy core and in MelonDS standalone get stuck on the boot screen in this new core (MelonDS DS). For example, Pokemon HeartGold and The Legend of Zelda: Phantom Hourglass. In Phantom Hourglass I get stuck on the very first screen you see with the ESRB notice and in Pokemon HeartGold I just get stuck on a white screen.

What should've happened instead?

The games should boot just fine because I’m using the official firmware/BIOS and checking the “Information” tab in Retroarch shows the correct BIOS are present and being used and when I open the same games in the legacy MelonDS core they boot up as expected.

Which platforms do you see the problem on?

• Windows
• macOS
• Linux
• Android
• iOS
• tvOS
• Other (specify below)

Which versions of the OS?

SteamOS

Which libretro frontend are you using?

Latest Stable Release

Terms

• I agree to follow the code of conduct.
• I understand that melonDS DS is not developed or maintained by the authors of melonDS.
• I understand that this form is for reporting bugs, not for requesting help.
• I understand that the author develops this core in his spare time, and that he is under no obligation to respond to this bug report.

[JesseTG]

Could you please post a log file with debug-logging enabled? You'll want to set the logging options like so:

This will provide information that may help me reproduce this issue. Thank you!

[ThisByzantineConduit]

Thanks for such a quick reply! Here is the log file generated using the logging settings you specified. I loaded Pokemon HeartGold in the core and it hung on the white screen again, and just to be sure it wasn't related to a past save state I restarted the emulation/console as well in the same log.
retroarch.log

[ThisByzantineConduit]

OK, I think I figured out what the issue was. By default the core had selected the firmware to use as "gc-dvd-20010831.bin", which is a GameCube firmware and not a DS firmware, but switching it to "firmware.bin" got those games to boot.

But this seems to be an issue others have experienced as well where melonDS DS defaults to incorrect firmwares for other systems, as reported in this other user's issue #183.

I've attached photos to show the list of BIOS file options I'm talking about.

[JesseTG]

Interesting. I should be stricter in checking the firmware's validity then, at least when picking a default. Since you've identified the cause as a known issue, I will close this ticket. If you have anything further to add, please do so in #183.