Quick Answer: NX2navi is an early-stage, fan-made static recompilation of Ocarina of Time that turns the game's code into a native x86-64 Windows application with a Vulkan renderer. It is not an emulator. You must supply your own legally obtained game dump, the project does not include game files, and the build runs on your own PC. It needs Windows 10 or later, a Vulkan 1.3 GPU, and about 30 GB of free space.
NX2navi is one of the more technically interesting fan projects in the Zelda community, and the project's GitHub repository is the place to read its details. Most people hear "port" and picture an emulator with a few settings bolted on. That's not what this is. The project takes a different route, and understanding that route explains almost everything about its performance, its requirements, and its limits.
Static recompilation is not emulation
An emulator runs the original machine code inside a software model of the console, translating or interpreting instructions while the game runs. A static recompiler works ahead of time. It takes the game's machine code and converts it into native code for your processor, so the result runs directly on the CPU as an ordinary Windows program.
That difference is why NX2navi can target 60 fps and higher on current GPUs without the overhead of simulating the hardware. It's also why the project's build step matters so much. The game is rebuilt on your machine from your files, not downloaded as a finished binary. Here's where people get tripped up: the speed comes from the native code, but the stability depends on how well that conversion handled every edge case in the original game. The README is honest about this. It lists a rare crash in the particle code and visual bugs as known issues.
What you need before you start
The project's own documentation is clear that you bring the game. The README states that no game files are included and that you need your own legally obtained copy, dumped from your own console. It also says the build contains the game, so the result is for your personal use and shouldn't be shared. Instructions for obtaining the files are not provided, and that's a deliberate boundary.
Once you have your files, the setup follows a straightforward sequence:
- Download
NX2navi-Setup-<version>.exefrom the project's releases page. - Place it next to your
.nupdump and run it. - Let the launcher download the build tools and compile the game, which takes roughly 10 to 25 minutes the first time.
- Start the game. Later updates rebuild only the parts that changed.
The setup isn't code-signed, so Windows SmartScreen will warn you on first launch. That's expected for an unsigned fan tool, but it's worth verifying you downloaded from the official releases page.
Hardware requirements, and what they really mean
The README lists the requirements in one dense paragraph. Here they are in a form you can check against your machine:
| Requirement | Stated value | What it means for you |
|---|---|---|
| Operating system | Windows 10 or later | No Linux or macOS support is stated |
| CPU | x86-64 with SSE4.2 | AVX2/FMA machines get a faster build |
| System RAM | 16 GB | Below this, the build and game are at risk |
| Free disk space | About 30 GB (game) + 1.5 GB (launcher and tools) | Plan for the full amount before starting |
| GPU | Vulkan 1.3, VK_EXT_external_memory_host, VK_EXT_mesh_shader | Older GPUs may lack the mesh shader extension |
The GPU row deserves attention. Vulkan 1.3 support is common on recent hardware, but the two extensions are the real gate. Check them before you spend time on the build.
Upscaling: where the common advice breaks down
The usual PC port advice is simple: pick the highest resolution your GPU can handle. NX2navi complicates that, and it's a good example of why the project's own design matters.
The project supports resolutions from 1800p up to 4K, 5K, or your window's native size. It also offers NVIDIA DLSS (DLAA, Quality, Balanced, Performance, and Ultra Performance on RTX GPUs) and AMD FSR 3.1 (on any GPU). These modes render the 3D scene at a fraction of the output resolution and keep the HUD sharp. For most players, a DLSS Quality or FSR 3.1 Quality setting at a high output resolution will look better and run faster than native rendering at a lower resolution.
Here's the counter-intuitive part. You might assume that a GPU with a lot of memory will automatically get sharper textures. NX2navi keeps the game's textures compressed in BC3 format by default. That roughly halves their video memory use at the same speed. The project only stops compressing if the PC has 20 GiB of video memory and 48 GiB of system RAM, because Windows counts video memory against the system's commit limit. In other words, more VRAM alone won't switch the feature on. The reasoning is memory safety, not just raw capability, and that's a trade-off you should understand before you tweak it.
Frame generation is the other feature people ask about. NX2navi offers AMD FSR 3.1 frame generation on any GPU, which inserts a generated frame between each pair the game draws and keeps the HUD out of it. The README says this gives about twice the frame rate on a fast display. NVIDIA's DLSS Frame Generation isn't offered yet, even though FSR 3.1 frame generation works on NVIDIA hardware too.
Known issues and real caveats
A responsible guide has to name the rough edges. The README lists three:
- First-start stutter. The first launch after an install or update, and the first visit to each area, can pause briefly while the graphics driver builds shaders it hasn't seen. Later starts are smooth. The project prepares shaders at build time and rebuilds pipelines in the background, but driver-side caching still takes a moment.
- A rare particle crash. The game's particle code can crash occasionally. Report it with details if you hit it.
- Visual bugs. Some are expected at this stage of development.
The stated playable areas are Kokiri Forest, Kakariko Village, Death Mountain Trail and its crater, the Temple of Time, and the Great Fairy fountains. Everything else should be treated as less tested.
Licensing: what you can and can't do
This section matters more than most readers expect. The project's source is public to read, but its additions and changes are all rights reserved. Under the project's LICENSE-ADDITIONS file, you can't copy or publish those additions without written permission. The base import stays under the MIT License, and third-party components keep their own licenses. The README also says no license grants anything for Nintendo's game.
NX2navi is an independent, non-commercial fan project and is not affiliated with or endorsed by Nintendo. If you're unsure whether your use fits, read the license files directly. This article is not legal advice.
Frequently Asked Questions
What is NX2navi Ocarina of Time?
NX2navi is a fan project that statically recompiles Ocarina of Time into a native Windows x86-64 application with a Vulkan renderer. It rebuilds the game on your own PC from your own dump, rather than emulating a console. It is in early development, so expect some visual bugs and occasional crashes.
How do I get NX2navi Ocarina of Time running on my PC?
Download the setup executable from the project's releases, place it next to your own .nup dump, and run it. The launcher downloads the build tools and compiles the game in about 10 to 25 minutes the first time. You'll need Windows 10 or later, 16 GB of RAM, around 30 GB of free space, and a Vulkan 1.3 GPU with the required extensions.
Does NX2navi include the game?
No. The project contains no game files. You must supply your own legally obtained copy of the game, and the build creates the playable result from those files on your machine. The README asks users not to share the built output.
Why isn't more video memory automatically better in NX2navi?
By default, NX2navi keeps textures in compressed BC3 format, which roughly halves their memory use at the same speed. The project only disables compression on machines with 20 GiB of video memory and 48 GiB of RAM, because Windows counts video memory against the system's commit limit. More VRAM alone won't change the texture format.
Is NX2navi safe to run given the unsigned installer?
The setup is not code-signed, so Windows SmartScreen will warn you on its first start. That warning is expected, but you should only download the installer from the project's official releases page and check the version you're getting before you run it.
Try this before you commit an afternoon
Don't start the full download and build without checking your hardware. Open the project's GitHub repository, read the requirements section, and confirm that your GPU supports VK_EXT_mesh_shader and VK_EXT_external_memory_host under Vulkan 1.3. Then check your free disk space against the 30 GB requirement. If everything lines up, run the launcher once and note how long the first build takes on your machine. Pass this to a friend who keeps asking whether their PC can handle a native Zelda port.