-
Notifications
You must be signed in to change notification settings - Fork 556
New issue
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
New Super Mario Bros 2 crashing with luma 10.0 and 10.0.1 #1281
Comments
Also not using any cheats or custom modules, just luma and the game. |
Same with Super Mario Maker in old 3DS |
Ok, so @lucasaf04 , are you sure its the exact same error screen and what were you doing right before it crashed? |
and can you also test on luma 9.1 please |
Is this a cartridge, or a digitally purchased game? If the latter, would it be possible for you to check your SD card for errors, or try a different SD card? |
this seems to be an issue related to luma 10 itself , errdisp crash screens will not show properly and appears fucked up. |
Yes, same error. @GlazedBelmont |
yeah, as I said, you two are actually getting normal errdisp errors if we call them so, but the errdisp error screens probably broke with luma 10+ |
im getting similar errors when booting up heroes of ruin, its also an errdisp |
Should probably be fixed by latest commits? |
I still experience random crashes in the older versions and latest versions of luma3ds. In the latest releases the crash shuts the system down and you'll need to replace all the luma3ds files for the handheld to boot again. I tested versions 11, 12.0.1, 13.0.1, 13.1.2 |
The game is just playing normally and then it crashed with errDisp:
I never had this issue with luma 9.1 but also dident play the game much there so I may have just never triggered it, it did happen twice in 2 days though and I played < 2 hours each time.
This crash has happened twice now causing loss of save data both times.
First time was on 10.0, second was on 10.0.1, both give the same error.
Firmware 11.10.0-43U, New 2DS.
The text was updated successfully, but these errors were encountered: