We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.0.1
The game boots to a white screen on standalone desktop melonDS, same issue on the unofficial android port.
Game boots to an error message about save data that cannot be accessed (there is not save present)
https://gist.github.com/GlaZedBelmont/8269ea73fd47da9294214bab98e2b17e here's a logcat
Device is AYN Odin 2, game works in Drastic, was previously broken in MelonDS, here's the issue related to it: melonDS-emu/melonDS#1358
Game should be booting to the titlescreen
Android 13
Retroarch 1.16.0
The text was updated successfully, but these errors were encountered:
Closing as I just went and grabbed the patch from https://projectpokemon.org/home/files/file/2466-pok%C3%A9mon-blaze-black-pok%C3%A9mon-volt-white/ and applied the Full one to a fresh copy, it boots now.
Sorry, something went wrong.
No branches or pull requests
What version of melonDS DS are you using?
1.0.1
Does the problem happen in standalone melonDS?
The game boots to a white screen on standalone desktop melonDS, same issue on the unofficial android port.
What happened?
Game boots to an error message about save data that cannot be accessed (there is not save present)
https://gist.github.com/GlaZedBelmont/8269ea73fd47da9294214bab98e2b17e here's a logcat
Device is AYN Odin 2, game works in Drastic, was previously broken in MelonDS, here's the issue related to it: melonDS-emu/melonDS#1358
What should've happened instead?
Game should be booting to the titlescreen
Which platforms do you see the problem on?
Which versions of the OS?
Android 13
Which libretro frontend are you using?
Retroarch 1.16.0
Terms
The text was updated successfully, but these errors were encountered: