External sysmodule loading is unavailable if loading a NATIVE/SAFE_FIRM older than 3.0.0. name.cxi: Any builtin sysmodule can be loaded externally, i.e.safe.firm: SAFE_FIRM, NATIVE_FIRM for the 3DS' Safe Mode.agb.firm: AGB_FIRM, used for Gameboy Advance Virtual Console games.twl.firm: TWL_FIRM, used for DSiWare and DS games.native.firm: NATIVE_FIRM, the main firmware.Supported external FIRMs and sysmodules are: You can override the EmuNAND to take the NATIVE_FIRM from by holding down a button on the D-Pad Up, Right, Down, Left for EmuNANDs 1, 2, 3 and 4 respectively.Įnable loading external FIRMs and modules: When enabled, this option will look for FIRMs and sysmodules (builtins only!) in /luma/ and /luma/sysmodules to load from the SD card instead of the versions on NAND.If this option is off, holding R will boot EmuNAND with sysNAND's NATIVE_FIRM.Use EmuNAND FIRM if booting with R: If this option is enabled, the EmuNAND's NATIVE_FIRM will be used if R is held, even if booting into sysNAND. To use a non-default EmuNAND, hold down a button on the D-Pad: Up, Right, Down, Left for EmuNANDs 1, 2, 3 and 4 respectively. You can boot into sysNAND by holding the L button if this option is enabled vice versa if it's disabled. Note: Clock/L2 are also toggleable once the 3DS is already booted, via Rosalina.Īutoboot EmuNAND: If this option is enabled and an EmuNAND is present on your SD card, the default EmuNAND you've selected will be booted by default instead of sysNAND.Clock+L2: The previous two options, combined.L2: The New 3DS' extra L2 cache will be enabled for games that do not normally support it.Clock: The New 3DS CPU will run at 804MHz instead of 268MHz even in games that are not New 3DS-enhanced if this option is selected.Off: Clock/L2 not forced, stock system behavior.This can have performance benefits but a few rare games have stability issues with it. New 3DS CPU: Force the higher clock rate and/or extra L2 cache even on games/applications that do not officially support it. Even Luma3DS installed in FIRM0/1 isn't completely "safe" it could be bypassed easily with ntrboot or similar methods. Note: This is more effective as child-proofing than as a complete theft deterrent a thief could bypass this as easily as deleting Luma3DS' configuration files, changing the boot.firm payload on the SD card (or, if using Luma3DS on CTRNAND, inserting an SD card with a boot.firm on its root, since boot9strap shows priority to the SD card.Off: No PIN enabled, continue boot normally.A message can be displayed on the bottom screen at the PIN input screen by placing a text file named pinmessage.txt in /luma (800 characters maximum!). PIN lock: Require a PIN to be entered before continuing boot. 7: Display the splash screen for seven seconds before continuing boot or chainloading a payload.5: Display the splash screen for five seconds before continuing boot or chainloading a payload.3: Display the splash screen for three seconds before continuing boot or chainloading a payload.1: Display the splash screen for one second before continuing boot or chainloading a payload.Splash duration: The duration of the splash screen can be configured with this option.
Screen brightness: Choose one of four different brightness levels for the config menu and chainloaded payloads. The Luma3DS v10.x configuration menu on Old 3DS/2DS not all features discussed appear in this screenshot.ĭefault EmuNAND: If you have more than one EmuNAND on your SD card, you can choose the one Luma3DS will default to by using the A button to cycle between EmuNANDs one through four. Each option is explained in the config menu itself on the bottom screen when highlighted. Otherwise, you need to hold Select while turning the 3DS on with the power button to trigger the menu. If this is your first time using Luma3DS or you have updated to a version of Luma3DS with a different config version, the menu will be shown automatically. Luma3DS has various optional features that are configurable via its config menu.
0 kommentar(er)
