A suitable PC
Review the documented operating system, processor, memory and Vulkan graphics requirements. A familiar GPU name alone does not establish compatibility.
System requirements overview ↗A FIELD GUIDE TO NATIVE PC PLAY
Understand the project. Prepare your setup.
Find your way to a native PC experience.
NX2navi uses static recompilation to turn the supported Switch 2 version of Ocarina of Time into a native PC application, using your own compatible game files.
Independent guide · No game files hosted or included

THE PROJECT
Think of NX2navi as a path from one supported game to a native program on your computer. It is a static recompilation project, rather than a general-purpose Switch 2 emulator. The distinction matters when choosing files, checking hardware and comparing other PC projects.
This NX2navi guide, also known by the spaced name “NX2 Navi,” brings those decisions into one place. Start with the overview, then choose the topic that matches your next task. The official repository remains the source for project code and developer documentation.
FROM FILES TO PC
A local process, with your own files at its starting point.
NX2navi prepares a build on your machine. The resulting game is for your own use and should not be shared. This diagram explains the concept; it does not describe how to obtain game data.
BEFORE YOU BEGIN
Check these foundations before starting an NX2navi installation.
Review the documented operating system, processor, memory and Vulkan graphics requirements. A familiar GPU name alone does not establish compatibility.
System requirements overview ↗NX2navi needs player-supplied game data matching its supported inputs. Check compatibility before building; the software download does not include the game.
Game file overview ↗Use the official NX2navi repository and release instructions to identify the intended installer. Avoid choosing a file based only on a download button.
Download safety overview ↗YOUR FIRST STEPS
Take one stage at a time. Keep the build process separate from the game you launch afterwards.
Find NX2navi on GitHub Releases and read the instructions for choosing the appropriate package.
Prepare compatible inputs and follow the Windows launcher through validation and the local build.
Review NX2navi display and input preferences. Keep a backup before editing configuration files.
Check your controls after launch, then use the relevant troubleshooting topic if a problem appears.
MAKE ROOM FOR YOUR SETUP
NX2navi brings PC-oriented choices into the experience. Understand what a setting changes before deciding whether it suits your system.
Resolution, aspect ratio and presentation settings shape the picture. Explore graphics options for hardware-dependent choices such as upscaling and HDR.
NX2navi documents keyboard, mouse and gamepad input. Use the controls overview to find layouts and remapping topics.
The NX2navi settings menu and INI reference serve different levels of control. Use configuration guidance to make deliberate, reversible changes.
CHOOSE YOUR PATH
Treat each operating environment as its own setup decision.
The primary documented NX2navi installation path uses the project’s launcher to prepare a local build.
Windows setup overview ↗NX2navi Linux packaging and source-build requirements need their own dependency and driver checks.
Linux overview ↗A handheld profile is not proof of complete support. Check SteamOS-specific evidence before assuming a working path.
Steam Deck overview ↗WHEN SOMETHING STOPS YOU
An NX2navi problem is easier to investigate when you know where it begins. Keep the error message and relevant log, then choose the matching topic.
THE GUIDE DIRECTORY
From first install to a familiar setup, explore the NX2navi topics below.
Choose the right files and understand the path to your first launch.
Identify authentic NX2navi release assets and choose the package intended for a new installation, rather than a launcher update.
Follow the NX2navi setup journey from preparing compatible files to the local build, first launch and initial configuration.
Check CPU, memory, storage and Vulkan requirements against the documented release before deciding whether your PC is ready.
Understand supported game inputs, file compatibility and validation messages, with no game data supplied or linked by this website.
Check the source of an NX2navi installer and understand what security warnings and available file hashes can tell you.
Find your platform, then work through display, input and configuration choices.
Separate AppImage packaging from source builds, identify toolchain dependencies and check the documented limits for your Linux system.
Understand SteamOS setup considerations and distinguish an NX2navi device profile from evidence of successful operation on the actual hardware.
Explore keyboard, mouse and gamepad configuration, button layouts and remapping, with input checks for a controller that does not respond.
Understand the NX2navi settings menu, configuration file and overrides, then back up your preferences before making a focused change.
Learn how display resolution, upscaling, frame generation and HDR differ, and why available options depend on hardware and software support.
Start with the symptom and the stage where it happens.
Investigate NX2navi frame pacing, first-visit pauses and resource limits while keeping developer benchmarks separate from results on your own system.
Distinguish a startup black screen from temporary black frames or a cutscene problem, then find the relevant checks and evidence.
Identify the NX2navi build stage that stopped and use its log to narrow down file, download, toolchain or storage problems.
Separate startup exits from gameplay crashes and collect the system details, reproduction steps and logs needed for a useful report.
Find the roles of active saves, exports and backups in NX2navi, and understand the risks before importing or replacing progress.
Follow project changes and compare the documentation behind each port.
Understand NX2navi release notes, launcher updates and rebuilds, with attention to preserving saves and configuration before changing an existing installation.
Compare two separate native PC projects through their documented setup paths and requirements, without assuming a universal performance or compatibility winner.
A LITTLE PERSPECTIVE
NX2navi and Hookshot are separate PC recompilation projects. Their setup paths and requirements deserve a source-based comparison, rather than an assumed winner. Choose by the documented fit for your hardware and the workflow you can follow.
Explore the comparison topicA FEW USEFUL ANSWERS
The essentials about NX2navi,
without the guesswork.
NX2navi is a project that recompiles the supported Nintendo Switch 2 version of Ocarina of Time into a native PC application. It uses game files supplied by the player.
No. Static recompilation translates supported game code ahead of execution. A general console emulator serves a different purpose: recreating a console environment for multiple games.
No. The project does not include Nintendo game data. You need your own legally obtained, compatible files; this website does not provide files, keys or instructions for obtaining them.
No. The software is an independent fan project. This guide website is also independent and is not maintained or endorsed by Nintendo or the software development team.
Use the Releases section of tangerineturtle1/NX2navi on GitHub. Read the developer's release instructions before choosing an asset, and follow external download links only after checking their destination.
GO TO THE SOURCE
Use the developer’s NX2navi documentation for source material and software reports.
This website is an independent guide, separate from the NX2navi developers and Nintendo. It hosts no game data, keys or software mirrors. Project and game names belong to their respective owners. Guidance is based on published documentation, not a claim of testing on your hardware.