Config
Config is a configuration program for CTR that can be used for things such as calibrating the touch panel and Circle Pad, and for setting the system clock.
| Button | Operation |
|---|---|
| ↑↓ | Navigate menu |
| A | Select / Run |
| B | Back / Cancel |
Initializes all settings. Settings are reset to their initial (default) values on the next reboot.
On first startup, initialize the settings and then configure them as needed.
| Button | Operation |
|---|---|
| X | Run |
| B | Cancel |
The following settings are initialized:
Calibrates the touch panel and Circle Pad.
| Button | Operation |
|---|---|
| A | Run |
| B | Back / Cancel |
To calibrate the touch panel, use the stylus to touch the + marks in sequence on the lower screen. Touch the + mark twice to complete the calibration process and save the calibrated settings.
To calibrate the Circle Pad, slowly move the pad around in the biggest circle possible. Finally, press the A Button to complete the calibration process and save the calibrated settings.
If you move the Circle Pad too quickly or if the circle motion is not complete, calibration will fail.
Configures the system clock. Time can be set in range of the years 2000 to 2050.
| Button | Operation |
|---|---|
| ←→ | Move between settings |
| ↑↓ | Adjust date and time |
| A | Set |
| B | Cancel |
Changes the system clock without affecting the RTC offset value.
If the nn::cfg::CTR::GetUserTimeOffset function is being used in the application to detect whether the user has changed the system clock, this provides a way of changing the system clock without the application knowing. When you change the RtcRaw value, the system clock also gets changed by that same amount. So, for example, if you advance the RtcRaw value ahead by one year, the system clock also gets advanced by one year.
The time of the system clock after the change is shown in the Rtc item.
The RtcRaw value can be set in the range of years 2001 to 2050.
When checking the setting, note that the system clock must be in the range of 2000 to 2050.
| Button | Operation |
|---|---|
| ←→ | Move between settings |
| ↑↓ | Adjust date and time |
| A | Set |
| B | Cancel |
Configures the LCD flicker adjustment and backlight settings.
| Button | Operation |
|---|---|
| ↑↓ | Move between settings / Change setting values |
| A | Select |
| B | Back |
Displays a calibration image (vertical black and white stripes) covering the entire screen that you want to calibrate. Adjust the value so that the calibration image does not flicker. If the image appears to flicker, the flicker setting needs adjustment.
Enables/disables the active backlight.
Sets screen brightness to one of five levels. The larger the number, the brighter the setting.
Configures the user information.
| Button | Operation |
|---|---|
| ↑↓ | Move between settings / Change setting values |
| A | Select / Confirm |
| B | Back / Cancel |
| Touch Panel | User name input |
Allows you to input a user name via a software keyboard. Only single-byte alphanumeric characters can be entered and displayed.
Toggles the user name profanity flag.
Select the country ID from the set list of country IDs for regions.
In addition to the country IDs defined for each region, you can also set an undefined ID (255).
Make sure to refer to and follow the guidelines when testing with undefined IDs.
For the region ID, select a value between 0 and 255.0 indicates that no region has been selected. 1 indicates that no selectable region exists.
All other values indicate that a specific region has been selected in the system settings.
If the ID is for an existing region, the ID and the region name are shown together.
"Undefined" is displayed for the ID where the regions do not exist (undefined ID.)
Make sure to refer to and follow the guidelines when testing with undefined IDs.
Configures other settings.
| Button | Operation |
|---|---|
| ↑↓ | Move between settings / Change setting values |
| A | Select |
| B | Back |
You can select monaural, stereo, or 3D surround sound for the sound output mode.
Configures the memory size.
You can switch the debugger between prod, dev1, and dev2 as needed.
Do not use any other settings unless instructed to do so.
Also, you cannot use any settings other than prod and dev2 on the development hardware or capture units.
prod uses 64 MB of memory, which is the same as the retail product.
dev1 uses 96 MB of memory, which is the size allotted for development.
dev1 mode.dev1 mode, you may not be able to place DLLs when only 32 MB or less of device memory is allocated.dev2 uses 80 MB of memory, which is the size allotted for development.dev2, but you cannot use the Internet browser.dev2 mode, you may not be able to place DLLs when only 16 MB or less of device memory is allocated.dev2, system applications may not function correctly when they are connected to debugging software.dev2, library applets cannot be launched when menu settings are specified in the HOME Menu.prod or dev2 is selected, menu settings are automatically changed to test menu.
Selects whether to enable or disable the application's handling of exceptions that arise in the non-debug environment.
Use the nn::os::SetUserExceptionHandler function to handle exceptions in the application.
If the application is not set to handle exceptions, the application quits when an exception occurs.
Selects whether to enable or disable stopping the application when a break is encountered in the non-debug environment.
If the application is not made to stop, it quits on a break.
Select either home menu or test menu for the menu to be started.
If HOME Menu is selected, the system mode is automatically changed to prod or dev2.
Set the language to one of the languages available for the given region.
The invalid setting is an invalid language code. Applications must operate normally even with this language setting.
Note: If an invalid language is selected, some of the application features other than starting the application from the HOME Menu may not operate correctly.
Select enable or disable to enable and disable Download Play debugging features.
After selecting enable, you can use the following debugging features.
pNotice argument in the nn::dlp::CTR::Server::Initialize function) to display the warning that a system update might be necessary on the client side.nn::dlp::CTR::Server::Initialize function reference for details.
Select enable or disable to enable and disable debugging functions.
Debugging is always disabled for retail products.
This setting affects the following functions.
nn::ac::DebugSetApTypenn::ac::DebugSetNetworkAreann::ac::DebugSetNetworkSetting1nn::cec::CecControl::StartScanningnn::cec::CecControl::EnterExclusiveStatenn::uds::CreateNetworknn::uds::ConnectNetworknn::hid::EnableSelectButtonnn::fs::InitializeLatencyEmulation
The impact of the setting varies depending on the function. For more details, see the specific function references.
Unless otherwise noted, the functions operate when set to enable and do nothing when set to disable.
Sets the delay time that is applied each time FS access occurs.
The behavior that occurs when there is a conflict between background FS access (such as with BOSS and FS access) in the application can be emulated.
The nn::fs::InitializeLatencyEmulation function must be called to enable this feature.
The specified delay time is routinely applied each time the FS is accessed. (No delay occurs when it is set to 0 ms.)
The recommended delay value is 700 ms.
Also, if the debugging mode is enabled, a random delay will occur in addition to the routine delay specified with this setting.
For more information, see the nn::fs::InitializeLatencyEmulation function reference.
This feature configures the COPPACS settings.
The COPPACS settings are only enabled for software for the Americas region, and when the country in System Settings is set to the US or Canada. You can change this setting to change the nn::cfg::CTR::GetCoppacsRestriction function's return value as shown below.
| Settings | Corresponding Return Values |
|---|---|
| "not restricted" | CFG_COPPACS_RESTRICTION_NONE |
| "need pin code" | CFG_COPPACS_RESTRICTION_NEED_PARENTAL_PIN_CODE |
| "need auth" | CFG_COPPACS_RESTRICTION_NEED_PARENTAL_AUTHENTICATION |
You cannot select the "need pin code" setting when Parental Controls have not been configured in the System Settings.
Tests the calibration and checks the settings.
| Button | Operation |
|---|---|
| A | Start |
| B | Exit |
Configures the EULA settings.
| Button | Operation |
|---|---|
| ↑↓ | Move between settings / Change setting values |
| A | Select / Confirm |
| B | Exit |
Checks the behavior of applications that use the stereo camera by rewriting and writing back some of the calibration values.
The following checks are supported. The check method is described later.
| Description of Check | Setting Displayed in Tool |
|---|---|
| Checks whether calibration data are used. | Set strange data 1 Set strange data 2 Set strange data 3 Set strange data 4 |
| Checks whether edge of screen is cut off in display with calibration limit values. | Set limit value 1 Set limit value 2 |
Reset to factory default item for resetting the rewritten calibration value.
Select one item from among the settings shown in the Please select box in the lower screen.
| Button | Operation |
|---|---|
| ↑↓ | Move between settings |
| A | Select / Confirm |
| B | Exit |
If you press the A Button and then successfully rewrite the calibration value, the word Success will display in the Result box in the lower screen. If the process fails, Failure will display.
The calibration values that are the targets of change are displayed in the bottom part of the lower screen as Current (for the current value) and After setting (for the value after rewriting). If the rewrite is successful, the current value will be updated.
The following table shows the correspondences between the setting item and the calibration value that is changed.
| Setting Name | Appearance on the Tool | Scale | RotationZ | TranslationX | TranslationY | AngleOfViewRight | AngleOfViewLeft |
|---|---|---|---|---|---|---|---|
| Invalid Value 1 | Set strange data 1 | Factory default value | Factory default value | Factory default value | 27.0 | Factory default value | Factory default value |
| Invalid Value 2 | Set strange data 2 | Factory default value | 5.0 | Factory default value | Factory default value | Factory default value | Factory default value |
| Invalid Value 3 | Set strange data 3 | 1.5 | Factory default value | Factory default value | Factory default value | Factory default value | 105.0 |
| Invalid Value 4 | Set strange data 4 | 0.66 | Factory default value | Factory default value | Factory default value | 105.0 | Factory default value |
Set any of Invalid Value 1, Invalid Value 2, Invalid Value 3, or Invalid Value 4 and close the tool. Next, start the application, go to a scene captured with the stereo camera, and confirm whether the positional relationship between the subjects in the left and right camera images is as indicated in the guidelines.
If the positional relationship between the subjects is as indicated in the guidelines, the calibration data is being used properly. If not, or if there is no change in the positional relationship between the subjects, the calibration data is not being used properly.
The calibration data values will no longer correspond to the cameras' actual physical relative positions. For this reason, the check described lets you verify the positional relationship between the subjects without the need to check whether stereoscopic display is working correctly.
The following table shows the correspondences between the setting item and the calibration value that is changed.
| Setting Name | Appearance on the Tool | Scale | RotationZ | TranslationX | TranslationY | AngleOfViewRight | AngleOfViewLeft |
|---|---|---|---|---|---|---|---|
| Limit value 1 | Set limit value 1 | 0.965 | 0.75 | -123.0 | -30.2 | 66.0 | 64.3 |
| Limit value 2 | Set limit value 2 | 0.965 | -0.75 | -123.0 | 30.2 | 68.7 | 66.0 |
Set limit value 1 or limit value 2 and then quit the tool. Now launch the application, move to a scene captured with the stereo camera, and check whether display shows without being cut off at the screen edge.
If limit value 1 or limit value 2 has been set, the calibration data values will no longer correspond to the camera's actual physical relative position. For this reason, the check described lets you verify whether edge of screen is cut off without the need to check whether stereoscopic vision is working correctly.
Conduct the above-described check using both limit value 1 and limit value 2.
On the selection screen, you can display the special settings items Set special limit value 1 and Set special limit value 2 by pressing the X Button while pressing Right on the +Control Pad. When either of these is selected, you can set a value larger than the calibration limit value. Use these settings when it is difficult to determine whether your application is behaving normally using the limit values as set forth in the Nintendo guidelines, or when you want to see how the application behaves when you intentionally set values greater than the limit values. You do not need to use these settings to check whether edge of screen is cut off.
After completing the check, select Reset to factory default so the calibration value is once again correctly associated with the camera's actual physical relative position.
Depending on the situation, use the System Settings application to make adjustments to the calibration data.
Rewrites and restores the gyro sensor and accelerometer calibration values.
| Button | Operation |
|---|---|
| ↑↓ | Move between settings |
| ←→ | Switches the gyro sensor / accelerometer settings. |
| LR | Batch-changes settings. |
| L/R + X | Batch-change the gyro sensor's RPM 0 item and the accelerometer's Offset item. |
| L/R + Y | Batch-change the gyro sensor's RPM Sensitivity item and the accelerometer's Scale item. |
| A | Select / Confirm |
| B | Exit |
Reads a settings file from an SD Card and uses this to configure the owner information, EULA, and Parental Controls.
| Button | Operation |
|---|---|
| ←→ | Switches the Result display pages. |
| A | Confirm |
| B | Back |
ctrsetting.txt) is located in the $CTR-SDK/resources/configtool/ directory.Do not change the name of the settings file. Any change to the format of the settings file prevents proper configuration.
Once configuration completes, the results are displayed on the lower screen. [o] : Configuration completed normally.
[x] : The system could not be configured, possibly because the information in the settings file was invalid.
[-] : The settings file did not contain a value specification for the particular item.
dev2 system mode setting and changed limitations on the setting range.COPPACS.ResetSetting.CONFIDENTIAL