3DS:Luma3DS/Configuration: Difference between revisions

Line 15:

==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.

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.

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.

Line 64:

Line 61:

====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====

Line 89:

Line 86:

====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).

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}}.

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====

{{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.

====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.

====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:

* 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==

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.

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.

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.

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

@@ Line 15: / Line 15: @@
 ==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.
@@ Line 64: / Line 61: @@
 ====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====
@@ Line 89: / Line 86: @@
 ====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}}.
@@ Line 103: / Line 100: @@
 ====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.
 ====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.
 ====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:
 * 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==
 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:
 * Booted from SD via B9S