Destroyed Options and usage (markdown)

Yuuki Hikari 2017-11-23 01:06:06 -05:00
parent 69c014699c
commit 856580bcee

@ -1,116 +0,0 @@
If you are booting Luma3DS for the first time, you will be greeted with the configuration menu.
If you want to open the configuration menu again, simply hold the **SELECT** button.
If the configuration file is incompatible with the current version, it will be automatically discarded.
![Config menu](http://i.imgur.com/jyMrgI1.png)
## Options:
- **Default EmuNAND**: Makes the selected EmuNAND the default.
You can override this setting on boot by holding down a button on the **directional pad**, **Up**, **Right**, **Down**, **Left** for EmuNANDs 1, 2, 3 and 4 respectively. If `Autoboot SysNAND` is off and you have a matching directional pad payload to use with the chainloader (refer to the [Other features and notes](https://github.com/AuroraWright/Luma3DS/wiki/Other-features-and-notes) page), also hold **A** to override the EmuNAND.
---
- **Screen brightness**: Change the screen brightness for Luma3DS and payloads.
The brightness is updated "in real time".
---
- **Splash**: Toggle the **splash screen** (refer to the [Other features and notes](https://github.com/AuroraWright/Luma3DS/wiki/Other-features-and-notes) page) and choose if displaying it before launching payloads (this is intended for splash screens that display button hints) or afterwards.
---
- **PIN lock**: This enables you to set a button combination (using **A**, **B**, **X** and **Y** and the **directional pad** as keys) that will be asked each time you'll boot your 3DS or Luma3DS.
Set this to **Off** to delete the existing PIN.
You can choose the amount of digits between **4**, **6** and **8**.
You will be allowed to change the PIN (can be skipped by pressing **START**) when quitting the configuration menu.
A message can be displayed on the bottom screen when the PIN is being asked by placing a text file named `pinmessage.txt` in `luma` (with 800 characters maximum).
---
- **New 3DS CPU**: Exclusive to **New 3DS** consoles.
This allows you to configure the processor the same way NTR CFW does:
- **Off** disables the patch.
- **Clock** enables New 3DS clock speed for all games.
- **L2** adds extra cache to the CPU _(Don't use this if your device crashes)_.
- **Clock+L2** enables the N3DS clock speed and adds extra cache to the CPU. _(Pick **Clock** if your device crashes)_.
---
- **Autoboot Emunand**: Determines if you want to boot **EmuNAND** or **SysNAND** by default (when **holding no buttons** on Luma3DS boot).
- If the option is **on**, **holding L** boots **SysNAND**.
- If the option is **off**, **holding L** boots **the default EmuNAND**. To use a different EmuNAND from the
default, hold a directional pad button (Up/Right/Down/Left equal EmuNANDs 1/2/3/4).
---
- **Use EmuNAND FIRM if booting with R**:
- **On**: uses the **FIRM from the default EmuNAND** to boot SysNAND **with R** (you usually can't boot a newer NAND with an older NATIVE_FIRM). You can override the EmuNAND to take the FIRM from on boot by holding down a button on the **directional pad**, **Up**, **Right**, **Down**, **Left** for EmuNANDs 1, 2, 3 and 4 respectively.
- **Off**: uses the **FIRM from SysNAND** to boot EmuNAND **with R** (you usually can't boot a newer NAND with an older NATIVE_FIRM).
---
- **Enable loading external FIRMs and modules**: If the option is **on**:
- If present in the `luma` folder, one of `firmware.bin`, `firmware_twl.bin`, `firmware_agb` and `firmware_safe.bin` (depending on the firmware being launched) will be used instead of the one stored in CTRNAND.
If using NUS-encrypted FIRMs, a matching **cetk** file for each encrypted FIRM is needed (`/luma/cetk`, `/luma/cetk_twl`, `/luma/cetk_agb`, `/luma/cetk_safe` respectively).
- If present in the `/luma/sysmodules` folder, standalone system modules will be loaded instead of the ones built-in to FIRM (not supported for SAFE_FIRM and NATIVE_FIRM versions older than 3.x).
---
- **Enable game patcher**: Enables the following features:
- The region/language emulation feature allows some games which need a specific language to be set to work, and **DLCs for foreign games** to load. To use it:
- Create a folder named **`titles`** inside `luma`.
- Create a folder with the game's **title id** as the name (look them up on **www.3dsdb.com**) inside `titles`.
- Create a file named **`locale.txt`** in the game's folder.
- Inside the file,
- Put **3 characters for the region** ("JPN", "USA", "EUR", "AUS", "CHN", "KOR", "TWN").
- Put **an empty space**.
- Put **2 characters for the language** ("JP", "EN", "FR", "DE", "IT", "ES", "ZH", "KO", "NL", "PT", "RU", "TW").
- For example, to play Pokémon™ Y in Japanese language and region:
- Create `0004000000055E00/locale.txt`.
- Put in `JPN JP`.
- Save.
- The LayeredFS feature allows you to replace RomFS files with files on the SD card for most games. To use it:
- Create a folder named **titles** inside `luma`.
- Create a folder with the game's **title id** as the name (look them up on **www.3dsdb.com**) inside `titles`.
- Create a folder called **`romfs`** in the game's folder.
- Put the replacement files in the `romfs` folder.
- For example, to use LayeredFS with Pokémon™ Y, make a folder named `romfs` , put your replacement files in it, then put `romfs` in `0004000000055E00`.
- The external .code feature allows you to use patched binaries for games. To use it:
- Create a folder named **titles** inside `luma`.
- Create a folder with the game's **title id** as the name (look them up on **www.3dsdb.com**) inside `titles`.
- Obtain a patched code.bin for the game, and put it into that folder.
- For example, to use a patched binary with Pokémon™ Y, rename it to `code.bin` and put it in `0004000000055E00`.
- The code IPS patching feature allows you to use IPS patches on a game's code. To use it:
- Create a folder named **titles** inside `luma`.
- Create a folder with the game's **title id** as the name (look them up on **www.3dsdb.com**) inside `titles`.
- Obtain an IPS patch for the game, rename it as `code.ips` and put it into that folder.
- For example, to use a patch with Pokémon™ Y, rename it to `code.ips` and put it in `0004000000055E00`.
---
- **Show NAND or user string in System Settings**: By default, this displays the current NAND/FIRM instead of "Ver." in System Settings.
- The strings that can be shown are:
- **Sys**: **SysNAND** booted with with its own FIRM,
- **Emu**: **first EmuNAND** booted with its own FIRM,
- **EmuX** (where **X** can be **2**, **3** or **4**): **EmuNAND X** booted with its own FIRM,
- **SysE**: **SysNAND** booted with the first EmuNAND's FIRM,
- **SyEX** (where **X** can be **2**, **3** or **4**): **SysNAND** booted with EmuNAND X's FIRM,
- **EmuS**: **first EmuNAND** booted with **the SysNAND FIRM**,
- **EmXS** (where **X** can be **2**, **3** or **4**): **EmuNAND X** booted with **the SysNAND FIRM**.
- You can also display a custom version string for each NAND, by creating text files named `customversion_sys.txt`, `customversion_emu.txt`, `customversion_emu2.txt`, `customversion_emu3.txt` or `customversion_emu4.txt` inside `luma`.
The version strings can't exceed **19 characters**.
---
- **Show GBA boot screen in patched AGB_FIRM**: If the option is **on**, the original GBA boot animation will be shown when launching a GBA game.
---
- **Patch SVC/service/archive/ARM9 access**: disables SVC, service, archive and exHeader ARM9 access checks (the service and archive patches don't work on New 3DS FIRMs between 9.3 and 10.4).
---
- **Set developer UNITINFO**: patches the value of CFG_UNITINFO sent to the ARM11 on boot to make applications believe they are running on a developer unit, and switches the CIA encryption to the developer one.
This makes ErrDisp display debugging information and allows you to install and run certain system software for development units, but also prevents using the eShop, amiibo, retail-encrypted CIAs etc.