3DS:Luma3DS/Configuration - Revision history

Cominou: update redirected link

2026-03-24T15:30:28Z

update redirected link

← Older revision		Revision as of 15:30, 24 March 2026
Line 109:		Line 109:

	==== plugin_loader_enabled ====		==== plugin_loader_enabled ====
	Determines if [[3DS:Game plugins/3GX\|3GX plugins]] placed in <code>SD:/luma/plugins/</code> are enabled.<br>Having this option disabled does not stop you from using [[3DS:Game plugins/~~PLG~~\|PLG plugins]] with bootNTR.		Determines if [[3DS:Game plugins/3GX\|3GX plugins]] placed in <code>SD:/luma/plugins/</code> are enabled.<br>Having this option disabled does not stop you from using [[3DS:Game plugins/NTR\|PLG plugins]] with bootNTR.

	==== ntp_tz_offset_min ====		==== ntp_tz_offset_min ====

ManiacOfHomebrew: Fix caps

2025-08-08T16:01:23Z

Fix caps

← Older revision		Revision as of 16:01, 8 August 2025
Line 34:		Line 34:

	====New 3DS CPU====		====New 3DS CPU====
	{{info\|This option can only be used on a ~~new~~ 3DS/2DS.}}		{{info\|This option can only be used on a New 3DS/2DS.}}
	When enabled, allows the New 3DS's enhanced clock speed and L2 cache to be used in all titles, not just New 3DS-exclusives. This may improve performance for some games, but it may also reveal hidden bugs in games when the Clock+L2 setting is enabled - this can result in anything up to a crash. This option is the same as the one found in the [[3DS:Luma3DS/Rosalina\|Rosalina menu]].		When enabled, allows the New 3DS's enhanced clock speed and L2 cache to be used in all titles, not just New 3DS-exclusives. This may improve performance for some games, but it may also reveal hidden bugs in games when the Clock+L2 setting is enabled - this can result in anything up to a crash. This option is the same as the one found in the [[3DS:Luma3DS/Rosalina\|Rosalina menu]].

Line 56:		Line 56:

	==== Redirect app. syscore threads to core2 ====		==== Redirect app. syscore threads to core2 ====
	{{info\|This option can only be used on a ~~new~~ 3DS/2DS.}}		{{info\|This option can only be used on a New 3DS/2DS.}}
	When enabled, Luma3DS will move some application threads to core2, which usually goes unused despite being intended for applications. This will boost performance on resource-intensive games (like Pokemon US/UM) by around 10%, but may also break some games and applications.		When enabled, Luma3DS will move some application threads to core2, which usually goes unused despite being intended for applications. This will boost performance on resource-intensive games (like Pokemon US/UM) by around 10%, but may also break some games and applications.

Aspect X: /* Troubleshooting with Luma3DS configuration */ typo

2025-05-11T07:44:23Z

Troubleshooting with Luma3DS configuration: typo

← Older revision		Revision as of 07:44, 11 May 2025
Line 172:		Line 172:
	** Indicates that Luma3DS is being booted from the <code>boot.firm</code> file on the root of your SD card, but that you are running B9S via ntrboot. If you're trying to install CFW, you should instead use SafeB9SInstaller as your <code>boot.firm</code> file.		** Indicates that Luma3DS is being booted from the <code>boot.firm</code> file on the root of your SD card, but that you are running B9S via ntrboot. If you're trying to install CFW, you should instead use SafeB9SInstaller as your <code>boot.firm</code> file.
	* Booted from SD via FIRM0 or FIRM1		* Booted from SD via FIRM0 or FIRM1
	** Indicates that Luma3DS has been installed to your FIRM partitions (where boot9strap or fastboot3DS would normally go). This is known to break some custom firmware functions, so unless ~~this~~ you intended to do this, you should [[3DS:Luma3DS to boot9strap\|follow these instructions]] to install boot9strap to your FIRM partitions.		** Indicates that Luma3DS has been installed to your FIRM partitions (where boot9strap or fastboot3DS would normally go). This is known to break some custom firmware functions, so unless you intended to do this, you should [[3DS:Luma3DS to boot9strap\|follow these instructions]] to install boot9strap to your FIRM partitions.
	* Booted from CTRNAND via FIRM0 or FIRM1		* Booted from CTRNAND via FIRM0 or FIRM1
	** Indicates that Luma3DS has been installed to your FIRM partitions and that the SD is not being read. You will need a usable SD card if you wish to install boot9strap to your FIRM partitions as above, so [[Formatting_an_SD_card\|try to fix that first by reformatting]] - if this does not work, your SD may be corrupted and should [[Checking_SD_card_integrity\|be tested for errors.]]		** Indicates that Luma3DS has been installed to your FIRM partitions and that the SD is not being read. You will need a usable SD card if you wish to install boot9strap to your FIRM partitions as above, so [[Formatting_an_SD_card\|try to fix that first by reformatting]] - if this does not work, your SD may be corrupted and should [[Checking_SD_card_integrity\|be tested for errors.]]

ItsCrocoSwine: reword /* Enable loading external FIRMs and modules */ as rverse is no longer available

2025-02-21T06:10:29Z

reword Enable loading external FIRMs and modules: as rverse is no longer available

← Older revision		Revision as of 06:10, 21 February 2025
Line 48:		Line 48:
	When enabled, Luma3DS will load customized FIRMs and system modules (basically, for modifying non-game elements on the 3DS). This option will not do anything unless you have the necessary files in <code>luma</code> or <code>/luma/sysmodules</code>.		When enabled, Luma3DS will load customized FIRMs and system modules (basically, for modifying non-game elements on the 3DS). This option will not do anything unless you have the necessary files in <code>luma</code> or <code>/luma/sysmodules</code>.

	~~You will~~ most ~~likely only use this option for specific applications like TWPatch (~~for ~~widescreen DS games) and rverse (a custom Miiverse server). For more information~~, ~~consult their respective installation guides~~.		This option is most commonly used for the Nintendo Network replacement [[Pretendo]], or sysmodule rewrites such as [[3DS:rehid\|rehid]] or [[3DS:Wumiibo\|Wumiibo]].

	====Enable game patching====		====Enable game patching====

ItsCrocoSwine: added plugin_loader_enabled and volume_slider_override + moved force_audio_output to config.ini only settings + removed a few extra spaces so section headers feel more attached to their sections

2024-09-02T20:40:12Z

added plugin_loader_enabled and volume_slider_override + moved force_audio_output to config.ini only settings + removed a few extra spaces so section headers feel more attached to their sections

← Older revision		Revision as of 20:40, 2 September 2024
Line 66:		Line 66:
	==== Show GBA boot screen in patched AGB_FIRM ====		==== Show GBA boot screen in patched AGB_FIRM ====
	When enabled, Luma3DS will show the [https://www.youtube.com/watch?v=6_ZD3FxMcvQ GBA boot screen] when loading a GBA game through the built-in GBA firmware of the 3DS (such as through virtual console).		When enabled, Luma3DS will show the [https://www.youtube.com/watch?v=6_ZD3FxMcvQ GBA boot screen] when loading a GBA game through the built-in GBA firmware of the 3DS (such as through virtual console).

	~~==== Force routing audio output through headphones ====~~
	Forces all audio output except for the camera shutter to go to the headphones. Because Luma3DS only directly affects NATIVE_FIRM, this will not work in DS games, GBA games, payloads such as GodMode9, or [[3DS:Safe Mode\|Safe Mode]].

	~~Due to software limitations, this will stop working temporarily if you unplug and then replug headphones. Close and reopen the screen when this happens to fix it.~~


Line 85:		Line 80:

	== Configuration options in config.ini ==		== Configuration options in config.ini ==

	As of Luma3DS v11.0, certain options have been moved and can only be edited in the <code>config.ini</code> file, located in both <code>SD:/luma/config.ini</code> and <code>[1]:/rw/luma/config.ini</code>. This section documents those options.		As of Luma3DS v11.0, certain options have been moved and can only be edited in the <code>config.ini</code> file, located in both <code>SD:/luma/config.ini</code> and <code>[1]:/rw/luma/config.ini</code>. This section documents those options.

Line 97:		Line 91:
	==== autoboot_dsi_titleid ====		==== autoboot_dsi_titleid ====
	Determines the DSi title to boot into when <code>autoboot_3ds_homebrew</code> is set to 2. The selected title must be installed on the NAND, or it will instead crash on boot - the default app used is {{GitHub\|devkitPro/nds-hb-menu\|nds-hb-menu}}.		Determines the DSi title to boot into when <code>autoboot_3ds_homebrew</code> is set to 2. The selected title must be installed on the NAND, or it will instead crash on boot - the default app used is {{GitHub\|devkitPro/nds-hb-menu\|nds-hb-menu}}.

			==== force_audio_output ====
			Forces all audio output except for the camera shutter to go to the headphones. Because Luma3DS only directly affects NATIVE_FIRM, this will not work in DS games, GBA games, payloads such as GodMode9, or [[3DS:Safe Mode\|Safe Mode]].

			Due to software limitations, this will stop working temporarily if you unplug and then replug headphones. Close and reopen the screen when this happens to fix it.


	=== Rosalina menu options ===		=== Rosalina menu options ===
	The following options can be altered in some way via the [[3DS:Luma3DS/Rosalina\|Rosalina menu]].		The following options can be altered in some way via the [[3DS:Luma3DS/Rosalina\|Rosalina menu]].


	==== hbldr_3dsx_titleid ====		==== hbldr_3dsx_titleid ====
Line 109:		Line 107:
	Determines what keys you need to press to open the Rosalina menu. By default, this is set to {{Key press\|L\|Down\|SELECT}}.<br>		Determines what keys you need to press to open the Rosalina menu. By default, this is set to {{Key press\|L\|Down\|SELECT}}.<br>
	For example, if one of the default keys is broken, you can set it to <code>X+Y</code> to change the menu combination to {{Key press\|X\|Y}}.		For example, if one of the default keys is broken, you can set it to <code>X+Y</code> to change the menu combination to {{Key press\|X\|Y}}.

			==== plugin_loader_enabled ====
			Determines if [[3DS:Game plugins/3GX\|3GX plugins]] placed in <code>SD:/luma/plugins/</code> are enabled.<br>Having this option disabled does not stop you from using [[3DS:Game plugins/PLG\|PLG plugins]] with bootNTR.

	==== ntp_tz_offset_min ====		==== ntp_tz_offset_min ====
	Determines your timezone to set the time correctly. The value is the number of minutes your timezone is from UTC.<br>		Determines your timezone to set the time correctly. The value is the number of minutes your timezone is from UTC.<br>
	For example, Eastern Standard Time (EST) is UTC-5, so the offset would be 60 * -5 = -300.		For example, Eastern Standard Time (EST) is UTC-5, so the offset would be 60 * -5 = -300.

			==== volume_slider_override ====
			Determines the volume to set the console to, overriding the physical volume slider of the console. Because Luma3DS only directly affects NATIVE_FIRM, this will not work in DS games, GBA games, payloads such as GodMode9, or [[3DS:Safe Mode\|Safe Mode]].

			The value should be a number from 0 to 100, while a value of -1 will disable the volume override.


	==== Screen filter options ====		==== Screen filter options ====
	All of the following options can be configured for each screen, and thus have two variables.		All of the following options can be configured for each screen, and thus have two variables.


	===== screen_filters_cct =====		===== screen_filters_cct =====
Line 137:		Line 142:
	=== Options you shouldn't touch ===		=== Options you shouldn't touch ===
	You shouldn't touch these options unless you know what you're doing.		You shouldn't touch these options unless you know what you're doing.


	==== autoboot_3ds_app_mem_type ====		==== autoboot_3ds_app_mem_type ====

StarlitSkies: s/Homebrew autoboot/Hbmenu autoboot to match current wording

2024-03-10T18:48:44Z

s/Homebrew autoboot/Hbmenu autoboot to match current wording

← Older revision		Revision as of 18:48, 10 March 2024
Line 37:		Line 37:
	When enabled, allows the New 3DS's enhanced clock speed and L2 cache to be used in all titles, not just New 3DS-exclusives. This may improve performance for some games, but it may also reveal hidden bugs in games when the Clock+L2 setting is enabled - this can result in anything up to a crash. This option is the same as the one found in the [[3DS:Luma3DS/Rosalina\|Rosalina menu]].		When enabled, allows the New 3DS's enhanced clock speed and L2 cache to be used in all titles, not just New 3DS-exclusives. This may improve performance for some games, but it may also reveal hidden bugs in games when the Clock+L2 setting is enabled - this can result in anything up to a crash. This option is the same as the one found in the [[3DS:Luma3DS/Rosalina\|Rosalina menu]].

	====~~Homebrew~~ autoboot====		====Hbmenu autoboot====
	When enabled, automatically boots to the selected homebrew launcher instead of the HOME Menu.<br>		When enabled, automatically boots to the selected homebrew launcher instead of the HOME Menu.<br>
	If 3DS is chosen, this will always be the normal Homebrew Launcher.<br>		If 3DS is chosen, this will always be the normal Homebrew Launcher.<br>

StarlitSkies: update info to match luma v13, swap a few {{B}} with {{Key press}}, minor misc. revisions

2023-08-23T04:42:23Z

update info to match luma v13, swap a few {{B}} with {{Key press}}, minor misc. revisions

Show changes

StarlitSkies: add features from luma v12

2023-02-16T04:35:31Z

add features from luma v12

Show changes

Ihaveahax: +Category:Nintendo 3DS guides; +Category:Nintendo 3DS information using HotCat

2023-01-20T01:11:47Z

+Category:Nintendo 3DS guides; +Category:Nintendo 3DS information using HotCat

← Older revision		Revision as of 01:11, 20 January 2023
Line 127:		Line 127:
	* Booted from CTRNAND via FIRM0 or FIRM1		* Booted from CTRNAND via FIRM0 or FIRM1
	** Indicates that Luma3DS has been installed to your FIRM partitions and that the SD is not being read. You will need a usable SD card if you wish to install boot9strap to your FIRM partitions as above, so [[Formatting_an_SD_card\|try to fix that first by reformatting]] - if this does not work, your SD may be corrupted and should [[Checking_SD_card_integrity\|be tested for errors.]]		** Indicates that Luma3DS has been installed to your FIRM partitions and that the SD is not being read. You will need a usable SD card if you wish to install boot9strap to your FIRM partitions as above, so [[Formatting_an_SD_card\|try to fix that first by reformatting]] - if this does not work, your SD may be corrupted and should [[Checking_SD_card_integrity\|be tested for errors.]]

			[[Category:Nintendo 3DS guides]]
			[[Category:Nintendo 3DS information]]

StarlitSkies: fix broken template (hopefully) and add more of them + more style fixes

2022-10-07T01:10:33Z

fix broken template (hopefully) and add more of them + more style fixes

← Older revision		Revision as of 01:10, 7 October 2022
Line 15:		Line 15:

	==Navigating Luma3DS configuration==		==Navigating Luma3DS configuration==
	{{info\|If your (Select), (Start), (D-Pad Up), (D-Pad Down), or (A) keys are broken, you will be unable to perform most functions in Luma3DS configuration. As an alternative, you can manually modify all options that are in the Luma3DS configuration by modifying the <code>config.ini</code> file in the <code>luma</code> folder (as of Luma3DS v11.0).}}		{{info\|If your {{B\|Select}}, {{B\|Start}}, {{B\|D-Pad Up}}, {{B\|D-Pad Down}}, or {{B\|A}} keys are broken, you will be unable to perform most functions in Luma3DS configuration. As an alternative, you can manually modify all options that are in the Luma3DS configuration by modifying the <code>config.ini</code> file in the <code>luma</code> folder (as of Luma3DS v11.0).}}
			You can access Luma3DS configuration by holding (Select) while powering on your device.<br>
	You can access Luma3DS configuration by holding (Select) while powering on your device.		When in the Luma3DS configuration menu, you can use the (Up) and (Down) D-Pad buttons to highlight different options. Press (A) to enable, disable, or cycle through the options. The currently highlighted option will be coloured a different colour from the rest of the configuration menu and an option that is currently enabled will be indicated with <code>(x)</code>. For example, <code>(x) Show NAND or user string in System Settings</code> indicates that the "Show NAND or user string in System Settings" option is enabled.<br>

	When in the Luma3DS configuration menu, you can use the (Up) and (Down) D-Pad buttons to highlight different options. Press (A) to enable, disable, or cycle through the options. The currently highlighted option will be coloured a different colour from the rest of the configuration menu and an option that is currently enabled will be indicated with <code>(x)</code>. For example, <code>(x) Show NAND or user string in System Settings</code> indicates that the "Show NAND or user string in System Settings" option is enabled.

	Once you are done configuring Luma3DS, press the (Start) button to save your configuration. If you have enabled a PIN, you will be told to set it; otherwise, the 3DS will reboot into the HOME Menu.		Once you are done configuring Luma3DS, press the (Start) button to save your configuration. If you have enabled a PIN, you will be told to set it; otherwise, the 3DS will reboot into the HOME Menu.

Line 64:		Line 61:

	====Autoboot EmuNAND====		====Autoboot EmuNAND====
	Determines whether EmuNAND will automatically boot when you turn on your 3DS without holding any buttons. If this option is disabled, you will boot into SysNAND by default. You can force the 3DS to boot into SysNAND, even with this option enabled, by holding ~~(Left Shoulder)~~ on boot, and vice versa.		Determines whether EmuNAND will automatically boot when you turn on your 3DS without holding any buttons. If this option is disabled, you will boot into SysNAND by default. You can force the 3DS to boot into SysNAND, even with this option enabled, by holding {{B\|L}} on boot, and vice versa.

	====Use EmuNAND FIRM if booting with R====		====Use EmuNAND FIRM if booting with R====
Line 89:		Line 86:

	====rosalina_menu_combo====		====rosalina_menu_combo====
	Determines what ~~key(s)~~ you need to press to open the Rosalina menu. By default, this is set to ~~(Left Shoulder)~~ + ~~(Down~~ D-Pad) + (Select).<br>		Determines what keys you need to press to open the Rosalina menu. By default, this is set to {{B\|L}} + {{B\|D-Pad Down}} + {{B\|Select}}.<br>
	For example, if one of the default keys is broken, you can set it to <code>X+Y</code> to change the menu combination to {{B\|X}} + {{B\|Y}}.		For example, if one of the default keys is broken, you can set it to <code>X+Y</code> to change the menu combination to {{B\|X}} + {{B\|Y}}.

Line 103:		Line 100:

	====use_dev_unitinfo====		====use_dev_unitinfo====
	{{warning\|This option will break most retail features while enabled ~~(including~~ online play, eShop, amiibo, and retail games)!}}		{{warning\|This option will break most retail features while enabled - this includes online play, eShop, amiibo, and retail games.}}
	When set to 1, this option changes a flag in the 3DS firmware so that it thinks it is a development unit, allowing you to run development applications.		When set to 1, this option changes a flag in the 3DS firmware so that it thinks it is a development unit, allowing you to run development applications.

	====disable_arm11_exception_handlers====		====disable_arm11_exception_handlers====
	{{warning\|This option normally does not stop errors from happening~~! It just shows a black screen or generic error message instead of the detailed error message, which~~ makes it harder to troubleshoot.}}		{{warning\|This option normally does not stop errors from happening - it only makes them harder to troubleshoot.}}
	When set to 1, this option disables the "An exception occurred" message that occurs when an application crashes, normally replacing it with a black screen or a generic error message.		When set to 1, this option disables the "An exception occurred" message that occurs when an application crashes, normally replacing it with a black screen or a generic error message.

	====enable_safe_firm_rosalina====		====enable_safe_firm_rosalina====
	{{info\|Luma3DS is not ~~meant to~~ touch SAFE_FIRM ~~due to its being intended~~ as a 'rescue mode' - it's relatively unlikely anything bad will happen, but ~~this still shouldn~~'t ~~be enabled unless you have~~ a specific ~~use for it~~.}}		{{info\|1=Luma3DS should not touch SAFE_FIRM since SAFE_FIRM is meant as a 'rescue mode' - it's relatively unlikely anything bad will happen, but don't enable this option without a specific good reason.}}
	When set to 1, this option does two things:		When set to 1, this option does two things:
	* Allows Rosalina to function when using [[3DS:Safe Mode\|Safe Mode]] (for example, if you need to take screenshots of Safe Mode or perform whatever other functions Rosalina allows)		* Allows Rosalina to function when using [[3DS:Safe Mode\|Safe Mode]] (for example, if you need to take screenshots of Safe Mode or perform whatever other functions Rosalina allows)
Line 118:		Line 115:
	==Troubleshooting with Luma3DS configuration==		==Troubleshooting with Luma3DS configuration==
	The Luma3DS configuration menu contains two pieces of information that can be used for troubleshooting: the currently installed Luma3DS version and the location from which Luma3DS is booting.<br>		The Luma3DS configuration menu contains two pieces of information that can be used for troubleshooting: the currently installed Luma3DS version and the location from which Luma3DS is booting.<br>
	If you are starting ~~fresh from~~ a new SD card or upgrading from an old (2017 or older) custom firmware setup, you can follow the instructions [[3dsguide:checking-for-cfw\|here]] to find out the correct course of action.<br>		If you are starting on a new SD card or upgrading from an old (2017 or older) custom firmware setup, you can follow the instructions [[3dsguide:checking-for-cfw\|here]] to find out the correct course of action.<br>
	As of Luma3DS v9.0, the location from which Luma3DS is booting will be displayed in yellow on the bottom screen. The following lines are known to be possible:		As of Luma3DS v9.0, the location from which Luma3DS is booting will be displayed in yellow on the bottom screen. The following lines are known to be possible:
	* Booted from SD via B9S		* Booted from SD via B9S