NX2navi · Windows · Vulkan
Install NX2navi on Windows from GitHub Releases
English guides for NX2navi, a native Windows x86-64 rebuild of The Legend of Zelda: Ocarina of Time for Nintendo Switch 2 (game version 1.1.1) with a Vulkan renderer. NX2navi-Setup lives on GitHub Releases; the launcher then builds from the dump already on this PC.
Setup and updates come from GitHub Releases for tangerineturtle1/NX2navi. Latest tag is read at request time.
Install path
Download only the Setup file
Use Direct download for NX2navi-Setup-<version>.exe. If that button fails, open the release and choose Assets. Ignore the app zip, runtime zip, and update.json unless you already know the launcher needs them.
Put Setup next to your dump
Keep the .exe beside the .nup the launcher expects. NX2navi’s git tree and Setup package are tools; the first run compiles a playable folder on this PC.
Run Setup and let the launcher build
Windows SmartScreen warns because the file is unsigned. Continue only when the file came from GitHub Releases. The first local build usually takes ten to twenty-five minutes.
Play, then use F1 for settings
After the first successful start, later launches skip the long rebuild. In-game settings open with F1. Performance overlay is F10. Updates can arrive through the launcher instead of a second Setup download.
What NX2navi is
NX2navi is a static recompilation of one Switch 2 title into a native Windows program. It is not a general emulator that you point at a library of ROMs. The published player path is a single unsigned Setup executable for 64-bit Windows. That installer places a launcher. The launcher finds your dump, downloads the tools it needs, compiles the game on your machine, prepares shaders, and starts the result. The built folder is produced on this PC from those files. The project asks you not to share that folder. These pages map download, first launch, F1, and the difference between Setup and a source checkout. The repository is tangerineturtle1/NX2navi; this domain is an English map of that repo, not Nintendo.
What you need before the first build
A normal NX2navi install does not start from Visual Studio. You need Windows 10 or 11 on an x86-64 CPU with SSE4.2. Machines with AVX2 and FMA get a faster generated build; older 64-bit chips that still have SSE4.2 still qualify. Plan about sixteen gigabytes of RAM, about thirty gigabytes free for the game tree, and about one and a half gigabytes for the launcher and its tools. The GPU must speak Vulkan 1.3 with VK_EXT_external_memory_host and VK_EXT_mesh_shader. Current NVIDIA and AMD cards that meet those extensions are the documented class. The launcher also looks for a .nup beside Setup. NX2navi will not run from a blank folder. Site email is for wording on this domain; app logs go to GitHub Issues.
| Need | Floor in the README |
|---|---|
| OS | Windows 10 or 11, 64-bit |
| CPU | x86-64 with SSE4.2; AVX2/FMA is faster, not a second download |
| RAM | 16 GB |
| Disk | About 30 GB for the game tree, 1.5 GB for the launcher |
| GPU | Vulkan 1.3, VK_EXT_external_memory_host, VK_EXT_mesh_shader |
| Game data | Your own .nup beside Setup — not inside the GitHub Asset |
Full wording lives on GitHub. This table is the player map, not a benchmark.
What the buttons on this page do
Direct download calls GitHub’s latest-release API and links the current Setup file when the name matches NX2navi-Setup-<version>.exe. When that request fails, the button becomes Open release Assets so you pick the file yourself. That recovery is intentional: this domain never keeps a stale copy. If you already have an older launcher, start that program and accept the update instead of downloading Setup again. First start after an update can rebuild shaders for about a minute and a half on the boot screen. That pause is expected.
| Asset on a typical tag | Who it is for |
|---|---|
| NX2navi-Setup-<version>.exe | New Windows install. The only player file this guide highlights. |
| NX2navi-app-*.zip | Launcher internals. Not a second game. |
| NX2navi-runtime-*.zip | Tools the launcher can fetch. Not Setup. |
| NX2navi-update.json | Updater metadata. Do not run it. |
If Direct download cannot see Setup, open Assets and pick by name.
Where the repository lives
The project is tangerineturtle1/NX2navi. README.md is the hardware floor and the player story. docs/launcher.md is the first-run build. docs/controls.md is F1, F10, keyboard, mouse, and pad layout. docs/building.md and docs/README-BuildKit.md are for people who skip Setup. LICENSE, THIRD_PARTY_NOTICES.md, and LICENSE-ADDITIONS are the legal files; this site paraphrases install steps and does not reprint those texts. If a sentence here disagrees with the README, the repository wins. App bugs go to GitHub Issues with logs\nx2navi.log from the game folder. Guide typos go to support@nx2navi.online.
- Binaries: GitHub Releases for tangerineturtle1/NX2navi
- App bugs: GitHub Issues, with a redacted log
- Guide corrections: support@nx2navi.online
Who these pages are for
Read this site if you already decided to try the published Setup on a Windows PC you control, you already have a dump the launcher can see, and you want a short map of filenames, SmartScreen, the first build, and how to roll back a tag. This is not a review, not a compatibility list for other games, and not a substitute for docs/launcher.md. Linux, macOS, and Steam Deck do not have a published player package in this guide. If you want to compile the port yourself, stay on Setup versus Source and then follow docs/building.md on GitHub.
What play looks like after the first build
Once the local build has finished, you are running native code, not an interpreter-style emulator loop. The cards below are the player-facing list from the README, not a promise that every GPU will hit every mode. Keyboard, mouse, and pads remap in F1. Stereo or 5.1 audio, docked or handheld presentation, and compressed textures unless the machine has a large commit limit, are documented upstream.
Frame pace
Sixty by default, or a cap from 30 to 240, the display refresh, or unlimited. FSR 3.1 can insert a generated frame; NVIDIA’s own frame generation is not offered yet.
Picture shape
The window can be widescreen or ultrawide. HUD, menus, and movies stay 16:9. Resolutions above 1440p include 1800p, 4K, 5K, or the window’s own size.
Upscaling
NVIDIA DLSS on RTX, or AMD FSR 3.1 on any GPU, with the HUD kept sharp. FSR 1 or bilinear can fill the window instead.
HDR and shaders
Native HDR or an enhanced path from SDR. Shaders are prepared at build time; pipelines met in play rebuild in the background so the game thread is not compiling.
Early development, not a finished store page
The README calls the project early and playable. Areas such as Kokiri Forest, Kakariko Village, Death Mountain Trail and crater, the Temple of Time, and Great Fairy fountains have been shown running at sixty frames per second and above on current GPUs, from the title screen and from saves. Visual bugs and occasional crashes are still expected. A rare particle crash, a brief hitch on first visit to an area, and the lack of NVIDIA’s own frame generation are listed in Known issues. Treat those as current facts, not as insults to your install. When two tags behave differently, say both version numbers on GitHub. Alpha software changes quickly, so an old forum post may describe a bug the current Setup already fixed. Check the Assets list before you assume a “corrupt” file needs a chat copy. If the launcher is clean and the window still will not open, the dump is usually missing, not a broken GitHub link.
FAQ
- Is nx2navi.online the official NX2navi website?
- No. The project lives on GitHub under tangerineturtle1/NX2navi. This domain is an English install and setup map of that repository.
- Does the download include the game?
- No. NX2navi ships tools. You supply a dump you already have. The game appears only after the launcher builds on your PC.
- Does NX2navi-Setup contain the .nup?
- No. Setup places the launcher. The launcher looks beside itself for a dump you already have, then compiles on this PC.
- Windows ARM, Linux, macOS, or Steam Deck?
- This guided path is 64-bit Windows. There is no Linux or macOS Setup described here.
- Where do software bugs go?
- File them on the NX2navi issue tracker. Include logs\nx2navi.log from the game folder.