NX2navi · Windows · Vulkan
Hardware floor
The published NX2navi player is 64-bit Windows with a Vulkan 1.3 GPU. This page restates the README floor as tables. It is not a laptop shopping list.
Setup and updates come from GitHub Releases for tangerineturtle1/NX2navi. Latest tag is read at request time.
What the README asks for
NX2navi Setup will not invent missing silicon. The numbers below are the project’s own floor for a first public player: Windows 10 or later, an x86-64 CPU with SSE4.2, sixteen gigabytes of RAM, about thirty gigabytes free for the game tree and one and a half gigabytes for the launcher, and a GPU that exposes Vulkan 1.3 plus two extensions. AVX2 and FMA machines get a faster generated build; that is a speed bonus, not a second GitHub Asset. ARM Windows and 32-bit Windows are not the file this guide highlights. If your PC fails the table, downloading Setup from a stranger will not add mesh shaders.
| Item | Documented floor | Notes |
|---|---|---|
| OS | Windows 10 or 11 | 64-bit only in this guide |
| CPU | x86-64 + SSE4.2 | AVX2/FMA is faster, optional |
| RAM | 16 GB | Compile and play both sit in memory |
| Disk | ~30 GB game + 1.5 GB launcher | Short local NTFS path |
| GPU | Vulkan 1.3 | See the extension table |
| Dump | Your own .nup | Beside NX2navi-Setup, not inside the Asset |
When this page and the README disagree, the README wins.
Vulkan extensions that actually matter
A card that “supports Vulkan” is not enough. The back end imports guest pools through VK_EXT_external_memory_host and draws with mesh shaders through VK_EXT_mesh_shader. Current NVIDIA and AMD boards that expose both are the documented class. An old integrated GPU that can open other Vulkan titles may still fail device creation. RenderDoc is called out upstream as blocking host-memory import, so a capture workflow is not a supported player path today. Driver reinstalls help when an update dropped an extension; they do not help when the hardware never had mesh shaders. File a GitHub issue with GPU name and driver version if you think the README is stale — not a zip of the game folder.
| API piece | Why NX2navi names it |
|---|---|
| Vulkan 1.3 | The renderer’s baseline |
| VK_EXT_external_memory_host | Guest memory import; RenderDoc hides this |
| VK_EXT_mesh_shader | Mesh shading path; missing = no device |
Disk, video memory, and commit limit
Windows counts video memory against the process commit limit. The project keeps the game’s textures compressed (BC3) unless the PC already has a large pool of video memory and system RAM — the README cites about twenty gigabytes of video memory and forty-eight gigabytes of RAM for the uncompressed path. Most people should leave compression on. Thirty gigabytes free is for the built tree, not for a second copy of Setup. Cloud-synced folders lock files mid-compile. Network drives add latency that looks like a random tool crash. Keep the dump, Setup, and output on a local volume. NX2navi is not a reason to format a drive you still need.
Local NTFS
Short path, not OneDrive, not a USB stick that sleeps.
Leave headroom
Shader caches and a second tag both grow. The 30 GB figure is a floor.
Do not share the tree
The built folder contains the game. It is for the PC that built it.
GPU memory
Compressed textures are the default. Uncompressed is a high-RAM option, not a download.
What this page will not certify
We will not publish a secret list of “this laptop SKU works.” Vendor names in the README (current NVIDIA and AMD cards with those extensions) are a class, not a shopping cart. If you are under the RAM floor, close browsers during the first build; that is common sense, not a new requirement. If you are on a handheld Windows PC, you still need the same Vulkan extensions as a desktop. Steam Deck is not a published install target here even if an ini comment mentions a device profile. This domain is an install map, not a hardware review site. Buy GPUs from vendors you trust, not from a comment that “Setup ran.” SSE4.2 is the CPU floor because the generated code uses it; AVX2 and FMA only change how fast that generated build is. Sixteen gigabytes is for compile plus play sitting in memory together. Thirty gigabytes is the built tree, not a second copy of Setup. Uncompressed textures are a high-RAM option the README cites around twenty gigabytes of video memory and forty-eight gigabytes of system RAM — leave BC3 on unless you already live in that class.
FAQ
- Does NX2navi run on Windows ARM?
- This guide only documents the x86-64 Setup. Do not rename an exe to look like ARM.
- My GPU plays other Vulkan games. Why would NX2navi fail?
- Mesh shaders and host-memory import are extra. Check the vendor’s current driver.
- Can I skip the disk requirement by deleting shaders?
- No. The first build writes a game tree. Clearing caches does not shrink the dump.