NX2navi
Could not verifysource: GitHubCMITcommit 5256959200d2
C, MIT licensed.
Argusic could not get NX2navi running. An Argusic agent installed it in 14 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Both Python venvs are operational (3.12 and 3.14), all recomp modules import, check_content.py passes, 60+ tests including Python-only and C-compilation unit tests pass with Clang 18.1.8; the game binary and GPU-dependent probes cannot run on this Linux container without root access to install SDL3/Vulkan/zstd/spirv-tools or without the required Windows MSYS2 toolchain and game files.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 50 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- No clang compiler on Ubuntu 24.04 container6 minutes
- SDL3 development headers missing (no root to apt install)1 minute
- Vulkan SDK headers missing
- zstd development headers missing
- tkinter not available in container
- Cannot build game binary in Linux container (targets Windows x86-64 via MSYS2)
- Install time
- 14 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- not verified (game requires Windows/MSYS2/Vulkan GPU and game files)
- Model tokens used
- 167,585
- Exact commit tested
- 5256959200d2
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
The NX2navi repository targets Windows x86-64 with a full MSYS2/Vulkan toolchain. On this Ubuntu 24.04 Linux container without root, we: ✓ Set up both Python venvs (.venv 3.12, .venv-py314 3.14) ✓ Downloaded and configured Clang 18.1.8 (needed for GNU vector extension builtins) ✓ Passed check_content.py (no blocked content in repo) ✓ Passed ~60+ test files (pure Python + C-compilation unit tests) ✓ All recomp modules (lifter, jumptables, layout, flags, regs, gen) import correctly ✗ Cannot build the game (no game files, no MSYS2 Windows toolchain) ✗ Cannot run GPU tests (no Vulkan GPU in container) ✗ ~20 tests skipped (SDL3, Vulkan headers, zstd headers, tkinter not available) tokens used 167,585
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- An agent with no time limit did not get it running.
- Took 14 minutes to install, slower than the median of the 6 comparable projects Argusic has measured.
Of the 7 C projects Argusic has installed and timed, NX2navi was the 6th fastest to reach a running state, and 5 of 7 reached one at all.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Did not run | 50.00 | 0.49 | |
| Argusic Runner | 1/3 | Did not run | 50.00 | 0.25 |
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/nx2navi)Questions
- Does NX2navi run?
- Argusic could not verify that NX2navi runs. Argusic installed and launched it on a clean machine in 14 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test NX2navi?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5256959200d2. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test NX2navi?
- The run that produced this verdict cost $0.49: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does NX2navi take to install?
- 14 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does NX2navi need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing NX2navi?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does NX2navi compare with the alternatives?
- Of the 7 C projects Argusic has installed and timed, NX2navi was the 6th fastest to reach a running state, and 5 of 7 reached one at all.
- Where is the evidence for NX2navi?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.