At a glance
- Project version, game update, program ID and main build ID identify different things.
- Renaming a file does not change its format or make an unsupported game version compatible.
- A successful native build still contains game-derived material and must not be redistributed.
What NX2navi game files are required?
NX2navi is a build/runtime project rather than a complete game package. Its Windows installer provides a launcher and prepares the tooling used on your machine. The game data is a separate prerequisite supplied by you; downloading another update ZIP does not substitute for it.
For the ordinary launcher path, prepare the supported .nup input and review the file selected in the first-run screen. The installation guide explains that selection step. This page concentrates on what compatibility means and how to classify a rejected input.
We do not link to game archives, key repositories or extraction services. This guide also does not describe console-protection bypasses or how to acquire the game data. Keep your original, legally obtained input intact while investigating its compatibility.
Supported game version and build identifiers
Use the identifiers from a matching release rather than a mixture of old tutorial screenshots and a development branch. The v0.8.0 player-facing Release and Build Kit reference the following game input. These identifiers let advanced users distinguish a game update from the project's own version number.
| Identifier | Player-facing v0.8.0 reference | Meaning |
|---|---|---|
| Game | The Legend of Zelda: Ocarina of Time, Nintendo Switch 2 version | The title/platform being recompiled; an original N64 file is a different input. |
| Game update | 1.1.1 | Version of the game input, not the NX2navi application. |
| Program ID | 0400486024DEC000 | Program identifier quoted by the Build Kit. |
| Main build | e0f3ccfa | Main-program build identification in that reference. |
| Launcher input | Compatible .nup | The normal Windows graphical installation path. |
| Other versions | Mismatches are refused by the documented player build | A newer-sounding filename does not prove compatibility. |
NUP, ExeFS and RomFS serve different input roles
The extension and directory names describe different forms of input, not interchangeable download choices. NX2navi game files accepted by the graphical launcher should not be confused with the inputs used by a manual build script.
The Build Kit documents --nup for a package input and --exefs together with --romfs for already available extracted folders. That does not establish a graphical launcher feature that selects any pair of folders. Use the commands belonging to the build method you intentionally chose.
| Input | Documented role | Common mistake |
|---|---|---|
.nup file | Package used by the normal player/launcher workflow. | Changing another extension to .nup and assuming the content changed. |
exefs folder | Program-side input for the manual Build Kit. | Supplying it as if it were a complete standalone game-data package. |
romfs folder | Resource-side input used with the manual program input. | Confusing it with the generated game's resource image or a save folder. |
| Source ZIP | Project source code rather than the user's game data. | Assuming repository code includes Nintendo's game assets. |
Check NX2navi game files before a full build
Begin with the path and the exact error category. A file that cannot be found, a package the tool cannot read and a recognized but unsupported game build are different situations. Repeating the same selection without reading the message does not tell you which one occurred.
Confirm the selected path
Check the filename and full folder location shown by the launcher. Make sure the input has finished copying or downloading from your own authorized source and is not a shortcut, split fragment or unrelated archive.
Confirm the intended workflow
Use a compatible NUP for the ordinary Windows launcher. If you deliberately use the manual Build Kit, read its input flags and requirements instead of applying graphical-launcher assumptions.
Compare the game identity
Check the supported game update and, where available, the program/build identification. Keep the project software version separate in your notes.
Read the validation result
Record the exact version, format or integrity message. Do not edit binary headers or identifiers to force a mismatch through the check.
py -I tools\make_game.py --nup "C:\path\to\your-game.nup" --out "C:\Games\Ocarina" --checkWhy NX2navi rejects a game file
Use the rejection as evidence about a particular stage. File size alone is a weak diagnostic: two different builds can have similar sizes, and an incomplete package can still have a plausible name. The tool's compatibility and integrity checks are more informative.
| Observed symptom | What to investigate | Useful next action |
|---|---|---|
| No dump found | Search location or selected path. | Select the intended local input explicitly and confirm it exists. |
| Wrong/unsupported version | The game update or program build differs. | Compare with the matching release's player requirements. |
| Unrecognized format | Input type is outside this workflow or cannot be read. | Distinguish NUP from archives, fragments and manual folders. |
| Integrity check failure | Content does not match what the tool expects. | Keep the exact message; inspect the original authorized copy without patching identifiers. |
| Validation passed; compilation later failed | Toolchain, memory, storage or another build stage. | Continue to installation errors, preserving the compiler/log details. |
Original inputs, native output and saves are separate
The local build produces executable code and resources derived from your game. A PC-format result does not remove the original rights in that material. The project's documentation asks you to keep the resulting game for your own use and not share it.
Keep NX2navi game files distinct from progress files. The original NUP is an installation input; the generated game lives in the chosen output folder; saves belong to the active profile structure. A backup of a save does not replace the game input, and a folder named saves is not a RomFS directory.
Once the setup is working, normal launcher updates and save management have their own workflows. Do not delete the original input, generated output or backup folders simply because their names look similar. Use save-file guidance before importing or moving progress.
COMMON QUESTIONS
Frequently asked questions
Which version is identified by the NX2navi game files reference?
The player-facing v0.8.0 documents identify the Switch 2 game update 1.1.1, program 0400486024DEC000 and main build e0f3ccfa. Those are game-input identifiers, not interchangeable project version numbers.
Can I use a different game update by renaming it?
No. Renaming changes a filename, not the underlying version or data. Read the validation message and the matching release's supported-input instructions.
Can the standard launcher take any ExeFS and RomFS folders?
The cited graphical workflow uses a compatible NUP. Separate ExeFS/RomFS flags are documented for the manual Build Kit; they should not be advertised as an arbitrary-folder feature of the launcher.
Does NX2navi download the game files for me?
No. It prepares software and a local build using compatible data you supply. This website does not provide Nintendo game data or links to obtain it.
Can I send my NUP or generated game with a bug report?
No. Report the version, error, environment and appropriate log excerpt. The project explicitly excludes game files, keys and generated game material from public reports and repository submissions.
SOURCE MATERIAL
Official sources
Use these project references to check the documented behavior and applicable software version. Hardware results and unresolved reports are identified in the relevant sections.