You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SysNAND version (+emu/redNAND version if applicable):
[e.g. 11.13.0-45U SysNAND, 11.13.0-45E EmuNAND]
Entrypoint (How/what you're using to boot Luma3DS): fastboot3ds
Luma3DS version: 13.1
Luma3DS configuration/options:
Default EmuNAND: ( )
Screen brightness: (4 )
Splash: ( x) after payloads
Splash duration: (3000 ms)
PIN lock: ( x) Off
New 3DS CPU: ( x) off
--
Autoboot EmuNAND: ( )
Use EmuNAND FIRM if booting with R: ( )
Enable loading external FIRMs and modules: (x )
Enable game patching: (x )
Show NAND or user string in System Settings: (x)
Show GBA boot screen in patched AGB_FIRM: ( )
Set developer UNITINFO: ( )
Disable Arm11 exception handlers: ( )
Enable Rosalina on SAFE_FIRM: ( )
--
Explanation of the issue:
Atempting to autoboot to TwilightMenu++ crashes on normal luma3ds. On a fork of luma, it works but with weird filters that change with user input. I will upload the crash dump from normal luma3ds later today.
Also, it might be a good idea to have a key combo to boot into TwilightMenu++, because very few people would want to always load into it. When you do want to load into it, you then can skip launching the home menu (which can take a while if your have a larger sd card) and then go straight to TwilightMenu.
Steps to reproduce:
Check the box to autoboot into DSi mode
Crash
Dump file:
The text was updated successfully, but these errors were encountered:
System model: New 3DS
SysNAND version (+emu/redNAND version if applicable):
[e.g. 11.13.0-45U SysNAND, 11.13.0-45E EmuNAND]
Entrypoint (How/what you're using to boot Luma3DS): fastboot3ds
Luma3DS version: 13.1
Luma3DS configuration/options:
Default EmuNAND: ( )
Screen brightness: (4 )
Splash: ( x) after payloads
Splash duration: (3000 ms)
PIN lock: ( x) Off
New 3DS CPU: ( x) off
--
Autoboot EmuNAND: ( )
Use EmuNAND FIRM if booting with R: ( )
Enable loading external FIRMs and modules: (x )
Enable game patching: (x )
Show NAND or user string in System Settings: (x)
Show GBA boot screen in patched AGB_FIRM: ( )
Set developer UNITINFO: ( )
Disable Arm11 exception handlers: ( )
Enable Rosalina on SAFE_FIRM: ( )
--
Explanation of the issue:
Atempting to autoboot to TwilightMenu++ crashes on normal luma3ds. On a fork of luma, it works but with weird filters that change with user input. I will upload the crash dump from normal luma3ds later today.
Also, it might be a good idea to have a key combo to boot into TwilightMenu++, because very few people would want to always load into it. When you do want to load into it, you then can skip launching the home menu (which can take a while if your have a larger sd card) and then go straight to TwilightMenu.
Steps to reproduce:
Check the box to autoboot into DSi mode
Crash
Dump file:
The text was updated successfully, but these errors were encountered: