At a glance
- The game's nx2navi.ini is separate from launcher data/launcher.json.
- OoT display controls are game_aspect and game_res; generic render_scale is not an equivalent option.
- An environment override or a different installation folder can explain an ineffective INI edit.
Where are NX2navi settings stored?
Open the game folder chosen during installation. The documented game configuration is nx2navi.ini, beside the native executable. If you have several installs, identify which one the launcher actually starts before editing. A correctly written change in an unused copy cannot affect the running game.
The launcher's own preferences are in data/launcher.json under the launcher installation. Those control launcher behavior, not the game's rendering configuration. Similarly, profile/ holds player-related data and is not a replacement configuration file. Do not delete the profile directory to reset one display preference.
The output path can be user-selected. A Windows launcher path under LocalAppData does not mean every generated game and every save lives there. The installation guide and save-file guide explain the separate locations.
Read the INI format and defaults correctly
The official example uses comments beginning with # or ;, section headings to organize settings, and named key/value pairs. Keys are case insensitive. Comments explaining a value are not another active setting; read the description before copying a line without its context.
A commented sample is not necessarily an explicit override in your own file. The selected device profile can supply defaults for values you have not set. Conversely, an old explicit value can continue to take precedence over a newly selected profile's default.
Do not replace the entire INI with a web preset. You can lose unrelated bindings, language choices and platform-specific values. Copy the original to a backup, change the minimum relevant line and preserve the explanation of what you intended to test.
# Example of a small, reversible change.
# Preserve the other settings in your own file.
fps_limit = 60
# Game-specific picture settings require a restart.
game_aspect = 16:9
game_res = 1440Common NX2navi settings and their effects
Match parameters to the release and platform you run. The v0.8.0 reference describes an FPS range of 30–240 plus display and unlimited choices, with an upper limit still applying and rates above 60 marked experimental. Raising the cap does not make the computer fast enough to sustain it.
The FPS limiter counts frames rendered by the game; generated frames can be added on top. Do not interpret a displayed generated-frame rate as an identical increase in game simulation speed. The performance guide explains how to build a useful comparison.
| Parameter | Meaning in the referenced configuration | Application / caution |
|---|---|---|
| fps_limit | Rendered-frame cap; example 60. | Live; above 60 is experimental, with matching realtime rules. |
| vk_present | Presentation choice such as mailbox or fifo. | Mailbox falls back when unavailable; use the exposed display setting. |
| fullscreen / window_size | Borderless fullscreen and window client size. | Documented live options; F11 toggles fullscreen. |
| game_aspect | OoT image shape, for example 16:9 or window. | Restart required. |
| game_res | OoT internal target height, for example 1440 or window. | Restart required; higher values increase workload. |
| device_profile | auto, desktop or deck starting defaults. | Read at startup; explicit values can override profile defaults. |
| menu_lang | Port menu language, such as en. | Separate from game lang / locale. |
| pad_layout / prompts | Physical layout / displayed glyph selection. | Different controls; prompt assets must be available. |
Why an apparently valid setting may do nothing
For OoT, the official INI says output_res and render_scale do not control the game's picture. These are different from unknown keys: a name can exist in the broader configuration yet be inapplicable to this game's rendering. Use game_aspect and game_res for the documented image controls.
Unknown or outdated keys do not gain meaning because another guide uses them. Check the matching configuration reference, the in-game menu and diagnostic log. A typo, an invalid value or a platform-only option should be investigated before adjusting several other settings.
A restart requirement is another common explanation. Editing a restart-only value while the process remains open does not demonstrate that the option is broken. Close the game normally, apply the small change and start that same executable again.
Environment overrides and device profiles
The reference documents corresponding NX2NAVI_* environment variables that override file values. Inspect launch scripts or Steam launch options if the menu/log shows a value different from the INI you just edited. Do not add more duplicate entries before checking the effective configuration.
The auto, desktop and deck profile choices are read at startup. Profile selection and explicit settings interact: a profile is a source of defaults, not a command to erase every previous user choice. The Deck profile's cap and core count are unmeasured starting points, as explained in Steam Deck compatibility.
Linux graphics libraries and frame-generation options also differ from Windows. A copied Windows DLL instruction or multiplier key is not automatically meaningful in a native Linux installation. Use the Linux guide and the platform-specific official reference.
Recover from an unsuccessful configuration change
A useful configuration experiment is reversible and answers one question. If a new setting causes a blank image, restore that setting from your known-working INI after closing the game. Keep the log and reproduction details before launching repeatedly; a crash can overwrite the most useful evidence.
The normal launcher update process preserves the INI, but your own backup remains valuable before manual edits or file replacement. Updating software, importing saves and copying a whole folder have different effects; do not infer that every operation is harmless because ordinary updates preserve settings.
Locate and back up
Confirm the running game's folder, close the game and copy nx2navi.ini somewhere identifiable.
Make one documented edit
Record the previous and proposed value and whether a restart is needed. Avoid a whole-file preset.
Observe the effective result
Restart if required, use the same scene, and inspect the menu/log for the actual value and errors.
Restore only what changed
If the result is worse, restore the earlier line or backup. Keep saves and caches intact unless a specific documented diagnosis calls for another action.
COMMON QUESTIONS
Frequently asked questions
Where is nx2navi.ini?
The documented game INI is beside the built native game executable in the selected output folder. The launcher's data/launcher.json is a separate file.
Do I have to edit the INI for ordinary settings?
No. Open the running game's settings with F1/Esc or the documented controller combination; many common choices have menu controls.
Why does render_scale not change OoT resolution?
The reference says this game uses game_aspect and game_res. The generic output_res/render_scale fields do not perform the expected picture control for OoT.
Can environment variables override NX2navi settings?
Yes. Corresponding NX2NAVI_* overrides take precedence. Check launch scripts and environment configuration when the effective value differs from the edited INI.
Will updating erase my settings?
The documented normal update workflow preserves the INI. Keep a backup before manual operations; that statement is not a promise about deleting folders or importing other data.
SOURCE MATERIAL
Official sources
Use these project references to check the documented behavior and applicable software version. Hardware results and unresolved reports are identified in the relevant sections.