Install NX2navi on Windows

Install path

1. 01

   Match the PC

   Use 64-bit Windows 10 or 11 on an x86-64 CPU with SSE4.2. ARM Windows is not the published Setup. Sixteen gigabytes of RAM and tens of gigabytes of free disk are the documented floor.

2. 02

   Download NX2navi-Setup

   Take NX2navi-Setup-<version>.exe from the latest tag. Compare the name. If Direct download fails, open Assets. Do not rename a zip to .exe.

3. 03

   Place it beside the dump

   Copy the Setup file into the folder that already holds your dump. Start it from that folder so the launcher can see the dump without a scavenger hunt.

4. 04

   Pass SmartScreen once

   More info, then Run anyway, only when you fetched that exact file from tangerineturtle1/NX2navi Releases. Then wait for the first local build.

The file you actually want

Windows players want one Asset: NX2navi-Setup followed by a version and .exe. That is the file NX2navi release notes tell new installs to run. The same tag may also list NX2navi-app-*.zip, a Python runtime zip, and NX2navi-update.json. Those files are not a second game. They exist so the launcher can keep the port current. If you download the app zip thinking it is the player, you will not get the guided first-run path. If Direct download on this page cannot see the Setup name, open Assets and pick it by eye. Trust the GitHub filename, not a forum screenshot of a renamed file.

SmartScreen and Defender

The Setup is not signed, so Windows SmartScreen warns on the first start. That warning is expected for this community build. Continue only when the hash and name match the GitHub Asset you opened. A warning after a download from an unrelated site is a reason to delete the file, not to click through. NX2navi is not a kernel driver and does not need you to turn off Defender globally. If a corporate PC blocks unsigned Setup files, that policy is outside this guide. Do not hunt “cracked NX2navi” packages. They are not a substitute for Releases.

The first local build

After Setup, the launcher finds the dump, downloads build tools, and compiles on this PC. Release notes describe ten to twenty-five minutes for that first pass, then shader preparation. Leave the machine plugged in. Closing the window mid-build does not produce a playable folder. When the game finally starts, later launches reuse that work. The first start after an update can prepare shaders again for about a minute and a half. Entering a new area can hitch while textures and pipelines appear. Those pauses are listed as known issues, not as a corrupt download.

1. Download NX2navi-Setup-<version>.exe from GitHub Releases
2. Keep it in the same folder as your existing dump
3. Start Setup, confirm SmartScreen only for that GitHub file
4. Wait for the launcher to build and to prepare shaders
5. Continue to Setup for F1 settings and nx2navi.ini

When Windows is the wrong page

If the launcher opens and then complains that it cannot see content, you are past install: go to Setup. If Vulkan extensions are missing, stay on Troubleshoot rather than downloading Setup a third time. If you wanted to compile from a git clone, skip this page and read Setup versus Source. Windows still needs your dump in every path. Prefer the filename on GitHub Assets over a renamed zip from chat.

CPU, GPU, and memory in one place

The published Setup targets x86-64 with SSE4.2. AVX2 and FMA machines get a faster generated build; that is a speed bonus, not a second download. 32-bit Windows and ARM Windows are not the file this page describes. Sixteen gigabytes of RAM is the documented floor because the local compile and the game both sit in memory. Video memory counts against Windows’ commit limit, which is why the project keeps textures compressed (BC3) unless the PC already has a large pool of video memory and system RAM. Vulkan 1.3, host memory import, and mesh shaders are hard requirements. A laptop that can play other Vulkan titles may still lack mesh shaders. Check the vendor’s current driver, not a five-year-old “works on my machine” comment. If the GPU fails the extension check, buying a second Setup from a stranger will not add silicon.

FAQ

Which NX2navi file do I run on Windows?

NX2navi-Setup-<version>.exe from GitHub Releases. Put it next to your dump.

Why does SmartScreen block NX2navi?

The Setup is unsigned. Continue only for the file you just took from the official Releases page.

How long is the first build?

Release notes describe about ten to twenty-five minutes once, then shader preparation. Later starts are shorter.