totk-pc-recomp
Static recompilation of The Legend of Zelda: Tears of the Kingdom to native Windows and Linux x86-64, with a Vulkan renderer. Game files not included.
Runs with mockssource: GitHubCMITcommit c38e0ca13d2b
C, MIT licensed. The project labels itself: game, linux, port, recompilation and windows.
totk-pc-recomp runs, with stand-ins for the services it depends on. An Argusic agent installed it in 47 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Two Python venvs set up, shader translator (totk_xlate) and hactool built, all no-game-file tests pass: SIMD differential (199900 cases, 0 fail), atomic differential (9900 cases, 0 fail), flags check (4M pairs, 0 mismatches), spin waits (8/8), romfs prompts (8/8), shader cache (5/5), xlate smoke (spirv-val OK). Full game build requires game ROM files not available in this environment.
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 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page. 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.
- Clang compiler not available in default environment5 minutes
- spirv-val not available for shader validation3 minutes
- .NET SDK 10 not installed2 minutes
- uv not found on PATH1 minute
- excl_mt ABA test fails on CAS-based exclusive monitor emulation1 minute
- Install time
- 47 minutes
- Cold machine to finish
- 48 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- CC=clang .venv/bin/python tests/diff/simd.py --encodings 2000 --cases 100 --jobs 2 --no-validity exited 0 with 199900 cases, 0 failing; .venv/bin/python tests/diff/atomic.py --cases 50 exited 0 with 198 tests, 9900 cases, 0 failing; .venv/bin/python tests/spin_waits_test.py exited 0 (8 passed); .venv-py314/bin/python tests/romfs_prompts_test.py exited 0 (8 passed); .venv/bin/python tests/flags_check.py exited 0 (2M+ operand pairs, 0 mismatches); .venv-py314/bin/python tools/xlate_smoke.py exited 0 (spirv-val OK)
- Model tokens used
- 398,771
- Exact commit tested
- c38e0ca13d2b
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- `romfs_prompts_test.py`: 8 tests passed - `pack_shader_cache_test.py`: 5 tests passed - `flags_check.py`: 0 mismatches at -O0 and -O1 (2M+ operand pairs each) - `diff/atomic.py`: 198 tests, 9900 cases, 0 failures - `diff/simd.py`: 2000 encodings, 199,900 cases, 0 failures (also validated 5000 encodings/499,900 … - `xlate_smoke.py`: shader translator + spirv-val pass - `excl_mt.py`: contention tests pass (ABA test fails due to CAS-based exclusive monitor limitation) **Could not verify:** - Full game build needs game ROM files (NSP/XCI + prod.keys) - not available - `diff/lift.py`, `diff/func.py`, `jumptables_check.py` need extracted ExeFS - `build_game.py` needs game files and MSYS2 toolchain (Windows-specific) - `totk.exe --selftest` needs the game build to exist
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 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 47 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 6 game projects Argusic has installed and timed, totk-pc-recomp was the 6th fastest to reach a running state, and 4 of 6 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.26 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/totk-pc-recomp)Questions
- Does totk-pc-recomp run?
- totk-pc-recomp runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 47 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test totk-pc-recomp?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c38e0ca13d2b. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test totk-pc-recomp?
- The run that produced this verdict cost $0.26: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does totk-pc-recomp take to install?
- 47 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 totk-pc-recomp need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing totk-pc-recomp?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does totk-pc-recomp compare with the alternatives?
- Of the 6 game projects Argusic has installed and timed, totk-pc-recomp was the 6th fastest to reach a running state, and 4 of 6 reached one at all.
- Where is the evidence for totk-pc-recomp?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.