OCARINA OF TIME / PC RECOMPILATION

NX2navi GitHub guide: Ocarina of Time on Windows and Linux

NX2navi is a static recompilation of Switch 2 Ocarina of Time 1.1.1 for x86-64 Windows and Linux. Its GitHub repository is tangerineturtle1/NX2navi. On Windows, download Setup and let the launcher build locally from your own game dump.

Guide reviewed 14 November 2026 · NX2navi 0.10.1 · Game 1.1.1 · Release notes & assets ↗

Ocarina of Time running in NX2navi 0.9.2 on Windows, with Link in a Kokiri Forest passage and the minimap visible.
Windows gameplay · NX2navi 0.9.2 / game 1.1.1. Community capture and hardware ↗

Does NX2navi work on Windows, Linux or Mac?

NX2navi 0.10.1 has Windows and Linux x86-64 packages. For an Apple silicon Mac, choose a separate Mac project for the edition you own: Ship of Harkinian for N64 Ocarina, or nxnative’s specific Switch 2 Ocarina profile.

WINDOWS x86-64

Use the NX2navi installer

Windows 10 or 11 is the main player workflow. Setup installs the launcher; your own game dump supplies the game. Follow the steps on this page.

Choose the Windows file →

LINUX x86-64

Use the separate AppImage build kit

The release also includes a Linux AppImage that builds locally. It uses Linux drivers and dependencies; the Windows installer is a different route.

Read the Linux branch →

For an iPhone or iPad, follow the device support of the separate Apple builder you choose. Compare NX2navi, nxnative, NX2Apple and Ship of Harkinian before downloading.

Which NX2navi GitHub file should you download?

The Windows player download is NX2navi-Setup-0.10.1.exe from the official GitHub release. Choose it for a new installation; the app and runtime ZIPs are updater components. If the direct link fails, open 0.10.1 → Assets and select the same filename. You do not need Git, Visual Studio or a manual Python installation for this player route.

NX2navi-Setup-0.10.1.exe
New Windows install. Installs the launcher and its build workflow.
NX2navi-app-0.10.1.zip
The launcher’s update payload. It is not a ready-built copy of the game.
NX2navi-runtime-py3.14.9-7a37dbc9.zip
A runtime the updater manages. Do not substitute it for Setup.
NX2navi-update.json
Updater metadata with release-file sizes and hashes; not a program to open.
NX2navi-Linux-0.10.1-x86_64.AppImage
The separate Linux build-kit route, described below.
Verify the Windows Setup download with PowerShell
In the folder containing the 0.10.1 Setup file
Get-FileHash .\NX2navi-Setup-0.10.1.exe -Algorithm SHA256

For this exact release file, the GitHub asset digest is:

0.10.1 Setup SHA-256
84f2aae815bdbce6c7b4d349a235f34a372300d10d77e4bf35eac71142507c11

A later Setup has a different digest. Compare against that later release’s asset instead of reusing this value.

Setup is unsigned, so Windows may show SmartScreen on first launch. Check the source, filename and file hash before deciding to run it. An unexpected antivirus detection or a different publisher is a reason to stop and investigate the file.

Which Ocarina of Time version and files does NX2navi need?

The game version is 1.1.1; the NX2navi program version is 0.10.1. Updating one does not update the other. Use files legally dumped from your own Nintendo Switch 2; this site and the project supply tools, not game dumps or keys.

Your game

  • Switch 2 Ocarina of Time with update 1.1.1.
  • Title ID 0400486024DEC000; the build kit identifies main build e0f3ccfa.
  • One prepared .nup is the normal launcher input. The manual kit also documents extracted exefs and romfs.

Your Windows PC

  • x86-64 CPU with SSE4.2; AVX2/FMA can use a faster build.
  • 16 GB RAM is the published floor. Large areas can still exhaust system memory.
  • Plan at least about 34 GB for the game plus 1.5 GB for tools, with additional room for your dump, saves and Windows.
  • Vulkan 1.3 and VK_EXT_external_memory_host. Mesh-shader-capable graphics are the standard route.

The 0.9.2 release introduced an optional Low-end GPU mode (experimental) for older cards, including a compute-based mesh fallback. It is off by default and does not remove the Vulkan or memory requirements. Use the version-specific settings below if this is your hardware. Keep the current automatic CPU helper-thread choice before importing older experimental settings.

What the launcher builds · workflow diagram
Your 1.1.1 dumpGame program + data→Local preparationTranslate, compile, prepare graphics→ocarina.exe + game dataKept on your own PC

How do I install NX2navi on Windows?

Run the official Setup, choose your supported .nup and output folder, then select Begin Installation. After the local build finishes, choose Play and open the running game’s F1 menu to continue with settings.

01

Keep Setup beside your own .nup

Put the downloaded Setup and your game’s .nup in the same folder, then start Setup. The default launcher location is %LOCALAPPDATA%\Programs\NX2navi. It does not normally require administrator rights.

02

Check Game Dump and Install Folder

The launcher looks beside Setup and in common folders. Select Game Dump to choose the correct file if it is not found. Select Install Folder to choose where the large built game will live. This is separate from the small launcher installation.

Actual English Game Dump field with Choose your .nup file.

Select Game Dump to choose the input

Game Dump · choose the correct input

The English 0.9.2 Game Dump row before a game is supplied. Select it to choose your supported .nup. Use Install Folder, described above, for the separate output destination.

Image source ↗
View the captured input control English NX2navi Game Dump row showing Choose your .nup file.Open full-size image ↗
03

Select Begin Installation and follow the named stage

The launcher gathers tools, inspects and unpacks the game, translates its code, compiles it and prepares shaders. Newer packages can also draw controller prompts and check the game files. Keep the computer powered and allow time for each stage; the source guide budgets 20–45 minutes for a first build, while individual release notes quote shorter examples.

The shader-preparation stage can continue even when its count pauses. Read the current stage and log rather than restarting the whole installation because a bar has briefly stopped.

04

Choose Play, then open F1

The launcher hides while the game runs and returns after it closes. Press F1 for in-game settings, or Minus + Plus on a controller. Start with a short baseline run before adding mods or experimental settings. Then follow the illustrated mod installation and load-order guide.

NX2navi settings: graphics, keyboard and controllers

Open the built game, bring its window to the foreground and press F1, or Minus + Plus together on a controller. Use Screen for graphics and Controls for inputs; launcher Settings handles updates and folders.

  1. Open Screen and choose a baseline

    Begin with the default 60 fps limit, a modest resolution and Texture detail on Automatic. Watch the F10 overlay while revisiting the same scene. Adjust one option at a time.

  2. Choose the upscaler that fits your GPU

    DLSS upscaling is for NVIDIA RTX cards. Windows also offers FSR 3.1; FSR 4 has its own supported Radeon/driver requirements. The Screen menu exposes the options available to the current build and hardware.

  3. Add frame generation after the base game is steady

    DLSS frame generation targets RTX 40/50 hardware; FSR frame generation uses a separate path. In 0.10.0–0.10.1, Windows frame generation can work with any Upscaling choice, including Native; the Linux NVIDIA path can still require DLSS upscaling at startup and a restart.

    The frame cap counts frames rendered by the game, with generated frames added above it. A displayed generated-frame total is not the underlying game rate.

  4. Map controls and match the prompts

    In Controls, select the input device, check each action and choose Nintendo, Xbox, PlayStation, Steam Deck or keyboard/mouse prompts when the build includes the prompt artwork. Some changes show after restart; use Restart to apply them.

What changes in the 0.10.1 Screen menu?

Upscaling → Native (100%)
Renders at the chosen game resolution without lowering the scene’s internal share. Choose it to compare a native-resolution baseline against DLSS or FSR.
Low latency
Enable it only when the driver offers the option; follow an “after restart” note. NVIDIA’s boost choice and AMD’s On choice differ. DLSS frame generation has its own latency handling, so a greyed-out row can be expected.
High frame rates
0.10.0 fixes several high-fps movement, moving-platform and sound problems. Update to 0.10.1 first, keep a steady 60 fps comparison, then raise the cap and revisit the same scene.

Graphics and timing changes in 0.10.0 ↗ · Adding a code mod? Follow the separate rebuild steps →

Set Ocarina’s resolution, ultrawide picture and HDR

Use F1 → Screen for the current controls. To edit the file directly, close the game and open nx2navi.ini beside the game executable. Keep a copy before changing it; a NX2NAVI_* environment variable overrides the matching INI value.

  1. Choose Game aspect and Resolution together

    Ocarina uses game_aspect for the shape and game_res for the picture’s height. For a 3440×1440 ultrawide display, start with 21:9 and 1440. The game reads these at startup, so restart after changing them.

  2. Check the actual game picture

    Supported heights are 1080, 1440, 1800, 2160, 2880 and window; the window choice has a 1440 minimum. output_res and render_scale do not set Ocarina’s picture size. DLSS/FSR render their share of the picture selected by game_res.

Example · 21:9 picture at 1440 height, restart to apply
[display]
game_aspect = 21:9
game_res = 1440

HDR · TONE MAPPED

Apply the current tone-mapped look

Enable HDR in Windows Use HDR, or use a Wayland compositor with HDR colour management. In Screen choose the tone-mapped HDR option; hdr = 1 applies live under the normal configuration.

HDR · NATIVE

Use the game’s own HDR mode

Choose native HDR, or hdr = native, then restart. Match hdr_peak_nits to your display’s peak; game and UI paper-white settings separately control their brightness.

If the menu says in use: off, check the OS/display HDR state first. If it says after restart, restart before comparing. The older hdr_tonemap, hdr_exposure and hdr_gamma keys are no longer read by this version.

I set hdr_live = 0. Why does switching HDR on need a restart?

That setting leaves the HDR path out of a run started in SDR. The default hdr_live = 1 keeps live switching available. Native HDR still has its own restart requirement.

Choose a frame cap that fits the display

Start with frame generation off and a rate the PC can hold. With fixed-refresh VSync, a cap that divides the display rate gives an even number of refreshes per game frame. At 120 Hz, 60 fps uses two refreshes per frame; 40 fps uses three. A 90 fps cap uses an uneven one-or-two pattern.

Illustrative cadence at fixed 120 Hz · each box is one refresh
60 fps
AABBCCDDEEFF
40 fps
AAABBBCCCDDD

For a 144 Hz fixed-refresh display, the source lists 72, 48 and 36 as even divisors. Variable refresh follows frames within its supported range. With frame generation on, the numeric cap still counts the game’s rendered frames; generated frames come on top. Keep the realtime and highfps_fix defaults enabled before testing above 60 fps.

Only Steam stutters? Compare launch methods → · Picture missing after a change? Start with the visual checks →

Keyboard prompts are drawn from the bindings during the build. After rebinding keys, Rebuild the Game can redraw them. For Steam Deck hardware and library setup, follow the Linux instructions below.

Which keys open menus, move Link and control the camera?

These are the documented default bindings for NX2navi 0.10.1. The game’s Swap Jump Controls option can exchange the jump/put-away actions; your own remaps also take precedence.

Default PC controls · read the action before changing a binding
ActionKeyboard / mouseController
SettingsF1 or EscMinus + Plus together
Performance overlayF10L3 + R3 together
Bug captureF8Use the keyboard while the game is focused
Borderless fullscreenF11Use the Screen menu
Move / cameraW A S D / mouse or arrow keysLeft / right stick
Interact / hold to dashE or Left ShiftSwitch A
Jump / put away or cancelSpace / Left Ctrl or BackspaceSwitch X / B
Sword / target / selected itemLeft mouse / right mouse or Z / F or XSwitch Y / ZL / ZR
Game menu / mapTab / MPlus / Minus

0.10.1 window keys ↗ · Full mapping reference ↗

Why are A/B or the button symbols wrong?

Button layout and Button prompts have different jobs. In Controls, layout decides how physical face buttons become Switch actions. Nintendo layout places Switch A on the east button; Xbox/PlayStation layout places it on the south button. Button prompts chooses the artwork displayed by the game.

  1. Match layout to the physical controls you want

    Choose Nintendo, Xbox, PlayStation or Automatic, then test confirm and cancel. Note any existing custom bindings before changing them; a physical button remapped by hand can keep overriding the selected layout.

  2. Change one binding in Controls

    Select its key or controller cell, press Enter or A, then press the new input. Esc cancels capture. F1, F8, F10, F11 and Esc are reserved utility keys.

  3. Choose matching button prompts and restart

    Pick the artwork for your pad or Keyboard and mouse, then apply the requested restart. After keyboard rebinding, Rebuild the Game redraws the prompt files. If the menu says prompt files are missing, check the build’s prompt-art step.

Older GPU settings: separate 0.9.2 advice from 0.10.1

Older 0.9.2 guides show F1 → Game → Low-end GPU mode (experimental). Current 0.10.1 source groups experimental replay/helper controls under Game → Testing; keep the automatic helper-thread value for the first comparison. Automatic can choose zero helpers on a small CPU or older Radeon.

  • Start with Screen → Texture detail → Low or Reduced and a modest game resolution when video memory is tight.
  • Change one option, restart when requested and revisit the same scene with F10.
  • If 0.10.0 gets slower as the camera moves, install 0.10.1 before changing memory or thread settings.
  • Use F8 to preserve a reproducible failure instead of copying a full set of experimental flags from another GPU.

What changed between NX2navi versions?

These are selected changes that affect installation and play. All rows refer to the NX2navi program; the required game remains 1.1.1.

Release → change → what to do
VersionChangeYour action
0.10.1 · 13 Nov UTCFixes video memory growing rapidly while walking or turning the camera in 0.10.0.Update 0.10.0 before tuning graphics. Only a few files compile again; existing game files and prepared shaders stay.
0.10.0 · 13 Nov UTCHigh-frame-rate movement and sound fixes; Native 100% scaling, expanded frame generation, low-latency controls and F8 bug captures.Older installations retranslate the game once. Use 0.10.1 for these features plus its memory fix.
0.9.2 · 12 NovOptional Low-end GPU mode, fixes for FSR mode-switch crashes, hidden-HUD upscaling and texture flicker.Update first if these symptoms match. Leave experimental GPU options off for the first baseline run.
0.9.1 · 12 NovLauncher Mods screen, more pipeline preparation and multi-core draw replay enabled by default.Use the launcher to manage mods; compare a clean run before diagnosing a modified game.
0.9.0 · 12 NovExpanded graphics and input work, including a fix for a resting or virtual gamepad axis unexpectedly taking control.Old controller reports may describe earlier behaviour. Retest input after updating.
0.8.0 · 11 NovFSR 4, initial fallback for GPUs without mesh shaders and several AMD/crash fixes.Check the newer 0.9.2 low-end route rather than copying old experimental flags.
0.7.0–0.7.1 · 10 NovLinux AppImage, save-sharing ZIPs, DLSS frame generation and lower-VRAM texture choices.Older videos may not show the current Saves screen or available graphics controls.
0.6.0–0.6.1 · 9 NovIncremental launcher updates preserve the compiled game and prepared shaders.Use Updates in your existing launcher; a fresh Setup is usually unnecessary.

Read the original release notes ↗. The current entry is 0.10.1, published 13 November UTC / 14 November Beijing time.

Will updating NX2navi delete my saves?

Normal launcher updates keep existing saves and settings. Export a save backup first, then use Updates while the game is closed. Updating the program rebuilds changed components; it does not install a different game update or replace your progress.

English Check for Updates at Start and Install Updates Automatically switches.

Automatic checks and installation are separate

English Keep Build Cache and Update Channel Stable rows.

Keep reusable work and choose Stable

Launcher Settings · updates and build cache

The 0.9.2 launcher’s English Settings view. Update Channel selects Stable or Preview; Keep Build Cache retains reusable compiled work. These are launcher choices, separate from the game’s F1 picture menu.

Image source ↗
View the complete window English NX2navi Settings with update channel, automatic updates and Keep Build Cache choices.Open full-size image ↗

Coming from 0.10.0

Use Updates to install 0.10.1. The memory fix recompiles only a few files; the compiled game and prepared shaders remain.

Coming from 0.9.2 or earlier

The 0.10 update translates the game’s code again for its frame-rate fixes. Let that stage complete. A longer update here is expected; keep the existing unpacked game data and your save export.

  1. Export progress and note the current version

    Close the game, open Saves → Export Save, and keep the ZIP outside the game folder. Record the current NX2navi version and your important settings in nx2navi.ini.

  2. Use Stable unless you chose a preview intentionally

    Open the launcher’s Settings. With update checks enabled, it checks on startup and periodically while open. If Install Updates Automatically is off, choose Updates yourself.

  3. Let the update finish while the game is closed

    The launcher can download an update during play, then installs it after the game exits. Existing unpacked game files and saves stay in place; only changed build work is repeated. Keep Build Cache makes future updates cheaper in time and disk work.

  4. Test the same save before changing other options

    Start the updated build, check F1 for the new program version, load your usual save and revisit one known scene. If an update was interrupted, use Rebuild the Game to finish rather than deleting the game folder.

Safe update sequence · workflow diagram
Export saveKeep a separate backup→Update + rebuildGame closed, existing data retained→Load and compareSame save, same settings

The launcher retains its current and previous application versions for startup rollback. That is separate from restoring an older playable game build or a save: keep your own save export even when automatic rollback is available. A first update from 0.5.0 retains its old generic CPU build until Rebuild the Game retunes it for this PC.

Where are NX2navi saves, and how do I back them up?

Open Game Folder in the launcher. NX2navi’s active save files are under profile\save\<account>\ inside that built game folder; profile\account.uid identifies the account. Use Saves → Export Save to back up the progress the game would load, including a completed save transaction waiting to be applied. Close the game first so its in-memory progress cannot overwrite restored files.

Actual English Choose a Zip and Choose a Folder controls in NX2navi.

ZIP and folder import have their own rows

Import · choose ZIP or extracted folder

The actual English import rows in the 0.9.2 Saves panel. Import a Save selects a ZIP; Import a Save Folder selects extracted progress. Keep these two routes separate.

Image source ↗
View the captured import controls English NX2navi Import a Save, Import a Save Folder and Open Saves Folder rows.Open full-size image ↗
Actual NX2navi Export Save Downloads choice and Add Log and Settings switch.

A save-only backup can leave logs out

Export · choose whether to include a report

Export Save writes a save ZIP. Add Log and Settings controls whether diagnostic files are included; turn it off for a save-only backup. Downloads is the default destination.

Image source ↗
View the captured export controls English NX2navi Export Save and Add Log and Settings rows.Open full-size image ↗

Make a private backup

  1. Choose Saves → Export Save.
  2. Turn Add Log and Settings off for a save-only backup, or leave it on for a report.
  3. Use Export To for another destination; Downloads is the default.
  4. Keep the exported ZIP outside the installed game folder.

Restore a NX2navi ZIP

  1. Quit the game and choose Import a Save.
  2. Select a compatible NX2navi save ZIP.
  3. Remember that a full ZIP replaces all save slots, not just the selected slot.
  4. The previous save is copied into saves\backup <date time> first. Start the game and check the result.

Have an extracted save or just one slot?

Import a Save Folder recognises supported console backups, nested emulator save folders and another NX2navi profile. A folder whose top level contains progress.sav is treated as one slot: its slot_00–slot_05 folder name selects the slot; otherwise the default is slot_00. Other slots remain in place.

Import pending, ZIP refused, or the game has no save yet?
  • An import started from the in-game menu applies on the next restart. Its “at next start” message is expected; restarting lets the game mount the imported save.
  • A ZIP for another game, an unsupported format, a damaged archive or a log-only report is not a valid save import. Choose the original save ZIP rather than renaming it.
  • Before the first save exists, a bug-report export can contain only the log and settings. Keep that report for diagnosis; create an actual in-game save before expecting a progress backup.
  • Use this project’s compatible Switch 2 save data. Ship of Harkinian uses a different N64-derived game and save format.

NX2navi troubleshooting: crashes, shaders and memory

Start with the stage that failed and keep its exact message. A rejected game update needs different steps from an unfinished build or a Vulkan crash after Play. For current 0.10.1, use the matching case below; older cases retain their version labels. Use the platform, version and symptom selector for an ordered plan and the correct log, or copy a support checklist if the problem continues.

The launcher rejects the game version
  1. Read the error for the expected game 1.1.1 and title ID.
  2. Check that the dump includes the right update, rather than just the base release.
  3. Update and re-dump your own game, then choose it in Game Dump. Updating NX2navi or renaming the file does not repair a mismatched game.
Installation stops at tools, compile or file checks
  1. Read the named failing stage and use Copy Report after the job fails.
  2. For a disk-space error, choose an output drive with enough free space. For a failed download, retry after checking connectivity.
  3. 0.9.2 fixes interrupted source generation being mistaken for a completed stage. Update before retrying that older failure.
  4. For damaged game data, follow the named file check and use a clean dump of your own game. A stand-in texture is not a repair of the original file.
Vulkan device lost, a crash at the title screen, or memory pressure
  1. Save a copy of logs\nx2navi.log before reopening the game. Record NX2navi version, GPU/driver, game version and the scene.
  2. Update the graphics driver and test current Stable with mods and frame generation off.
  3. Check the logged VRAM and system-commit messages. Use Low/Reduced texture detail for a small VRAM budget; close memory-heavy applications.
  4. For system commit low on a 16 GB Windows PC, review the upstream page-file guidance. It calls for a 32 GB-or-larger initial page file and sufficient disk space.
  5. Integrated AMD GPUs can fail because the host-memory heap is too small. Check the actual Vulkan extensions and the 0.9.2 low-end branch; lowering resolution alone does not change that heap.
Shader preparation repeats, or a new area briefly stutters

After a driver update, driver-side caches may need rebuilding. Leave preparation to finish. On NVIDIA, the upstream guide recommends NVIDIA app → Graphics → Global Settings → Shader Cache Size → Unlimited so prepared libraries are not repeatedly evicted. This is a driver cache; it is not your save folder.

New textures and pipeline variants can still cause a first-visit pause. Revisit the same route to distinguish this from a repeatable crash; keep the relevant log instead of erasing all caches as a first step.

FSR crashes when switching modes, or the picture becomes blocky with the HUD hidden

These match fixes in 0.9.2. Update first, then retest the same upscaling mode and HUD setting without unrelated changes. Keep experimental selective_motion and low-end options separate while diagnosing a baseline image problem.

The 3D scene turns black while the minimap stays visible

A 0.9.2 Windows report on an RX 580 2048SP shows the scene alternating between visible and dark while the HUD remains. Both frames below come from that same versioned report, using game 1.1.1.

NX2navi 0.9.2 community capture with the 3D passage and minimap visible.
The scene is visible.
NX2navi 0.9.2 community capture where the 3D world becomes dark while the minimap remains visible.
The 3D view is dark; the minimap is still drawn.

For this pattern, record the exact GPU/driver, game area and settings alongside logs\nx2navi.log. The report reproduces with bilinear scaling and FSR, so changing the upscaler alone is not a complete diagnosis. Use the support checklist to keep that context together.

How do I capture an NX2navi bug with F8?

  1. Capture the moment

    On 0.10.0 or 0.10.1, focus the running game and press F8 when the problem is visible. Wait for the “Bug capture … saved” note and keep its capture number.

  2. Open the complete capture folder

    Open the game’s log folder, then captures. Each numbered folder includes the frame, settings, recent log, frame timings and save export. capture.txt is written last and marks a complete capture.

  3. Attach the right context

    Tell the maintainer the capture number, NX2navi version and what happened. Review the folder before sharing: it contains a screenshot and game progress. The files stay on your PC until you share them.

F8 capture location · inside your built game folder
logs\captures\<number-date-time>\capture.txt
Only stutters when launched through Steam?

Compare the same save by starting the launcher directly, then through Steam, with the same settings. Issue #823 records this distinction on 0.10.0; a shader-precache change helped one reported setup. Preserve the launch-method difference in the report and retest the current release before changing global Steam settings.

Report a reproducible problem to the project’s GitHub Issues, using the requested report fields. Review logs and paths before sharing them; game files and keys are not needed in a report.

Can I use NX2navi on Linux or Steam Deck?

The 0.10.1 release includes NX2navi-Linux-0.10.1-x86_64.AppImage, a local build kit with its own Python and pinned Vulkan headers. Match the Linux prerequisites: x86-64 Linux 6.7+ with PAGEMAP_SCAN, Vulkan 1.3 graphics support, and the documented compiler and system libraries.

  1. Native AppImage: run the Linux build kit with the required drivers/libraries. It builds the game from your own input and writes a daily-launch script.
  2. Manual source build: install the documented compiler/libraries, then run the source command below. Use the resulting native executable from its own game folder.
  3. Windows through Proton: use the Windows package through the compatibility layer. Keep its Proton version, save location and reports separate from the native Linux build.
Native Linux AppImage · in the folder containing the download
chmod +x NX2navi-Linux-0.10.1-x86_64.AppImage
./NX2navi-Linux-0.10.1-x86_64.AppImage
Native AppImage route · build once, then launch the result
AppImage build kitPython + pinned headers~/Games/OcarinaBuilt game + dataplay.shDaily play / Steam shortcut

The kit defaults to ~/Games/Ocarina. Its play.sh changes into the game folder before starting ocarina. For a manual source build, use the documented command, then launch from that output folder:

Manual source workflow · after installing its prerequisites
python3 -I tools/make_game.py --nup "/path/to/your game.nup" --out ~/Games/Ocarina --jobs 4
cd ~/Games/Ocarina
./ocarina

The four-job choice follows the guide’s 16 GB RAM advice. The AppImage supplies pinned Python/headers, while drivers, compiler and the named runtime libraries still come from the system. Native Linux has separate NVIDIA DLSS libraries; Windows FSR 3.1/4 and frame-generation DLL routes do not apply to the native Linux build.

Add the finished native game to Steam

  1. Finish one direct launch first

    Run the built play.sh and confirm the game opens. On Steam Deck, use Steam → Power → Switch to Desktop for desktop file and library setup.

  2. Add the game, not the build kit

    In desktop Steam choose Add a Game → Add a Non-Steam Game → Browse. Select the finished game’s play.sh for the AppImage route. If browsing hides scripts, show all files. For a manual build, select ocarina and set the shortcut’s Start In folder to the game directory.

  3. Keep native and Proton shortcuts distinct

    The native Linux executable runs as Linux software. Use a separate Windows shortcut and its Compatibility/Proton choice only for the Windows route. On Deck, return to Gaming Mode and find the shortcut in the Non-Steam library.

Valve’s Desktop Mode and non-Steam guide ↗ · Direct launch works but Steam stutters? Compare these steps →

Which settings does the Steam Deck profile choose?

The current source detects Steam Deck hardware with device_profile = auto. For keys you have not set, it selects fullscreen, a 1280×800 window, a 40 fps cap and four game cores. These are the profile’s starting settings; use the F10 overlay to choose a cap your scene can hold.

Environment variable
Highest priority: a matching NX2NAVI_* launch variable overrides the file.
Your INI value
Explicit saved settings override automatic profile defaults.
Automatic device profile
Supplies the unset values. Ocarina’s actual game picture still uses game_aspect and game_res; a 1280×800 window does not set its render height.

Native Linux memory sharing

For non-NVIDIA graphics, the kit can use /dev/udmabuf when access and its memory limit are configured; otherwise it falls back to copying and names the reason in mem: log lines. Follow the exact prerequisites before changing system configuration. If play crashes, keep the native Linux device-lost context with the log.

For a native Mac, choose nxnative or the N64 Mac guide.

NX2navi, nxnative, NX2Apple or Ship of Harkinian?

For Hookshot's continuation on Windows or Linux, follow the Longshot launcher, build and save guide. It uses a separate Launcher/Builder release system. Its NX2navi save-import path covers profile selection and pending-save checks before copying progress.

For a Windows emulator workflow, use the Fritchii download, setup and save-migration guide. Its ready-made lichii.exe runs an emulator library; NX2navi builds the supported game locally. Fritchii’s Saves manager has its own Eden/Lichii copy and profile-repair steps.

Looking for the 3DS remake on Mac? Ocarina ReTuned’s Mac download and preparation guide uses your supported decrypted 3DS ROM. It is separate from this Switch 2 1.1.1 build and the N64 Ship of Harkinian route.

NX2navi GitHub and setup questions

Is NX2navi an emulator, and does it include the game?

NX2navi recompiles the supported Switch 2 game into native x86-64 code before play. Its download contains build tools and a launcher; your own legally dumped game supplies the program and data. The input-to-output diagram shows the local build.

Can I use my N64 ROM or Ship of Harkinian save?

NX2navi expects Switch 2 Ocarina of Time 1.1.1 and compatible save data for that game. A N64 ROM and Ship of Harkinian progress belong to a different edition. Use the N64 Mac guide for those files, or the NX2navi save-import steps for this project.

Do I need my dump again for every NX2navi update?

Normal updates rebuild from the game files already unpacked on disk. Keep the installed game folder and its build state; use Updates or Rebuild the Game to complete an interrupted update.

Can my 16 GB PC or Steam Deck run NX2navi at 60 fps?

Sixteen GB is the published RAM floor, and large areas can still create memory pressure. The default 60 fps limit is a setting, not a measured result for your PC. Start with the baseline graphics steps; Steam Deck users should also follow the Linux hardware and library branch.

Where are nx2navi.ini and the logs?

Open Game Folder in the launcher. nx2navi.ini is beside the executable; logs\nx2navi.log is the game log. Launcher logs are separate: use Settings → Open Logs Folder. Save the failed run’s log before reopening the game.

May I reuse code from the NX2navi GitHub repository?

The public repository has separate terms for its base import and later additions. Read the base licence and additions notice for the code you plan to reuse.

What details should I include when asking for help?

Give the NX2navi version, game update, operating system, GPU/driver and exact failing stage together. This lets a support forum or an AI chat choose steps for your actual setup. Copy this checklist and fill in the blanks; include only relevant log lines after reviewing local paths.

Copy a useful setup or crash report
NX2navi version: 0.10.1 (or your actual version)
Game edition and update: Switch 2 Ocarina of Time 1.1.1
Operating system: Windows or Linux, with version
CPU / RAM / GPU / driver: 
Stage: download / build / first launch / F1 settings / gameplay / save import
Exact error or symptom: 
Last action before it happened: 
Settings or mods changed: 
What I tried and what changed: 
Relevant log lines (review local paths first): 
Question: What is the next step for this version and stage?

Return to symptom-specific fixes → · Back up progress before trying another build → · Report a reproducible app problem on GitHub ↗

Sources and your next step

This guide follows NX2navi 0.10.1 and fixed source 5ae55db, reviewed 14 November 2026. Earlier launcher and community game images keep their 0.9.2 labels. The mod guide adds current English launcher controls and a worked load-order example.

Browse the project directory → · Choose the N64 Mac app → · Build with nxnative on Mac →