NX2navi · Windows · Vulkan
Troubleshoot NX2navi
Most NX2navi failures are the wrong Asset, SmartScreen on an unsigned Setup, a GPU missing Vulkan extensions, or a first-run shader pause. Logs live in the game folder.
Setup and updates come from GitHub Releases for tangerineturtle1/NX2navi. Latest tag is read at request time.
Setup will not start
Confirm the file is NX2navi-Setup-<version>.exe from tangerineturtle1/NX2navi Releases, not a zip renamed to look like Setup, and not NX2navi-app-*.zip. Run it from the folder that already holds your dump. If SmartScreen appears, use More info and Run anyway only for that GitHub file. If a browser marked the download as blocked, unblock the file in Properties or download again with a browser that did not quarantine it. Corporate allow-lists that reject unsigned binaries will not be solved by this website. Do not disable Windows security for the whole machine to “make NX2navi work.”
- Only Releases from tangerineturtle1/NX2navi
- Name must be NX2navi-Setup, then a version, then .exe
- Dump already in the same folder
Launcher starts, game does not
If the launcher cannot see a dump, it cannot invent one. If tools fail to download, check that GitHub is reachable and that a proxy is not eating the runtime zip. If the build dies halfway, disk space is the first check: the README’s thirty gigabytes is not a metaphor. Antivirus that locks the output directory mid-compile looks like a random compiler crash; exclude the game folder you created, not the entire drive. After a successful older tag, prefer the launcher’s own update. A mixed folder that contains both a git clone and a Setup tree is a support headache; pick one path.
Graphics, hitching, and known crashes
Vulkan 1.3 plus VK_EXT_external_memory_host and VK_EXT_mesh_shader are required. Integrated GPUs and older cards that lack mesh shaders will not become compatible because you downloaded Setup twice. Later starts are smoother than the first. Collect logs\nx2navi.log from the game folder before filing GitHub Issues. Follow CONTRIBUTING.md. Strip anything that looks like a dump path you would not post in public.
| Symptom | Usually |
|---|---|
| First boot hitch / new area hitch | Driver building pipelines or textures — known issue |
| Rare crash in particles | Upstream known issue — attach the log |
| No NVIDIA DLSS Frame Generation | Not offered yet; FSR 3.1 FG still runs on NVIDIA |
| Missing mesh shaders | GPU or driver, not a second Setup download |
Rollback and “I installed the wrong thing”
To leave a bad tag, open an older release and run that tag’s Setup. Do not install Setup from tag A and then overwrite random files from tag B’s app zip. If you meant to build from source, uninstall the confusion and read Setup versus Source instead of stacking toolchains. Linux and macOS questions do not have a hidden package on this domain; the answer is still Windows. Steam Deck is not a supported install target in this guide even if an ini comment mentions a device profile.
What to put in a useful issue
A useful report names the tag, whether you used Setup or a source tree, the GPU vendor and driver version, and the last lines of logs\nx2navi.log. Say whether SmartScreen was involved, whether this was a first install or an in-launcher update, and which area or menu you were in. Do not paste a wall of binary. If two machines differ, say so. If you already rolled back, say which tag still works. Maintainers cannot guess a missing mesh-shader extension from “it crashed.” CONTRIBUTING.md exists so you do not open a blank issue. This website’s inbox will not forward your log to GitHub for you. If the overlay in F10 shows a locked 1 fps after a driver rollback, include that number; it is more useful than a vague “slow.” Reinstalling Setup will not replace a driver. Write the issue in English if you can; maintainers already read logs more carefully than machine-translated novels. Known issues in the README still include a rare particle crash and a hitch on first visit to an area while pipelines appear. Those are not “wrong Asset” failures. Fog and lighting regressions that 0.5.0 restored are the reason you should name both tags if you jumped versions. RenderDoc hides host-memory import, so a capture session that “used to work in other Vulkan games” can still fail device creation here.
FAQ
- Where is the NX2navi log?
- logs\nx2navi.log inside the game folder the launcher created. Attach that to GitHub Issues.
- Can I email a crash log to support@nx2navi.online?
- No. That address is for this website’s copy. App crashes go to GitHub Issues with logs\nx2navi.log.
- Vulkan errors after a GPU driver update
- Reinstall a current vendor driver that still exposes Vulkan 1.3 and the required extensions. Setup cannot add mesh shaders to a GPU that lacks them. Then check F10 after a clean start from the same folder.