NX2navi · Windows · Vulkan
First-time setup
After Setup runs, the NX2navi launcher finds your dump, fetches tools, builds locally, and starts the game. Settings live in F1 and in nx2navi.ini.
Setup and updates come from GitHub Releases for tangerineturtle1/NX2navi. Latest tag is read at request time.
Install path
Confirm the dump is already there
The launcher looks beside itself for the dump. If that file is missing, the first build cannot start. NX2navi cannot invent the game from an empty folder.
Let the launcher finish once
The first run downloads tools and builds. Ten to twenty-five minutes is the range release notes use. Do not send the unfinished folder to another PC and expect it to play.
Open in-game settings
F1, or Minus and Plus together on a gamepad, opens the NX2navi menu. F10 toggles the performance overlay. Keyboard, mouse, and pads remap there.
Optional ini beside the exe
Copy nx2navi.ini.example to nx2navi.ini next to the game executable if you want file-based defaults. Environment variables named NX2NAVI_* override the file.
Order of operations
NX2navi setup is a short list once install succeeded. The launcher locates the dump, pulls the toolchain it needs, writes a game folder on this computer, prepares shaders, and starts play. Afterwards it can keep the port up to date and rebuild only what changed. That is the player story documented in docs/launcher.md. A separate BuildKit document describes doing the same build by hand. A third document describes compiling NX2navi from source. Most people should stay on the launcher. Hand builds and source checkouts exist for people who already read those files. Mixing a half-finished source tree with a Setup install in the same directory is a good way to confuse both paths.
What the launcher looks for
Setup here means point the launcher at files already on disk, wait for the local compile, then configure display, audio, and input. The README states that instructions for obtaining the dump will not be provided; these pages stay on launcher.md, F1, and nx2navi.ini. If a GitHub comment asks for a dump, do not forward it to support@nx2navi.online — that inbox is for this domain’s wording.
Settings you can change after it runs
The in-game menu covers frame limits from thirty to two hundred forty, the display refresh rate, or unlimited. Widescreen and ultrawide follow the window while HUD, menus, and movies stay sixteen-by-nine. Resolution can rise above the game’s 1440p. Upscaling includes NVIDIA DLSS modes on RTX GPUs and AMD FSR 3.1 on any GPU, with the HUD kept sharp. FSR 3.1 frame generation is documented; NVIDIA’s own frame generation is not offered yet. HDR can use the game’s native HDR or an enhanced path from SDR. Audio is stereo or 5.1. Docked and handheld console modes exist. Controls include rumble, gyro, Nintendo or Xbox layouts, and remapping. Fine defaults also live in nx2navi.ini.example. Prefer F1 while you learn; use the ini when you want a file you can copy.
| Where | What it changes |
|---|---|
| F1 | In-game settings menu |
| F10 | Performance overlay |
| nx2navi.ini | File defaults next to the executable |
| /controls | Keyboard, mouse, pad map on this site |
When setup is finished
Setup is finished when the rebuilt game window is up and you can open F1. It is not finished when Setup.exe only unpacked files. It is not finished if shaders are still compiling on the boot screen — wait. If the launcher loops because the dump is missing, you do not have a setup problem you can fix with a second GitHub zip. If Vulkan fails, go to Troubleshoot. If you intended a source build, leave this page for Setup versus Source. Keep the built folder private. The project states the result contains the game and is for your own use.
Input, audio, and the overlay after first launch
After the window is up, spend a minute in F1 before you assume a stick is broken. Pads can follow Nintendo positions or Xbox labels. The game follows whichever connected pad you press. Mouse can drive the camera; keyboard sticks are all-or-nothing unless you hold the walk modifier documented in controls.md. Rumble strength, gyro, and trigger rumble on pads that support it live in the same menu and in the ini. F10 is the overlay for frame time, not a cheat menu. Audio output is stereo or 5.1 depending on what Windows presents. If the picture is letterboxed inside a wide window, that is the documented choice to keep HUD at sixteen-by-nine, not a failed ultrawide hack. Change those options here; do not reinstall Setup to “reset widescreen.”
FAQ
- Does NX2navi need extra key files from this website?
- Follow the launcher’s prompts for files already on disk. These pages document Setup, F1, and the ini — not key extraction.
- Where are NX2navi settings?
- F1 in game, or nx2navi.ini next to the executable. See nx2navi.ini.example on GitHub for keys.
- Can I skip the long first build?
- No. The launcher builds from your dump on this PC. That pass is the product, not a download of the finished game.