Recompilation, not emulation
How a native recomp works
An emulator reads the console program instruction by instruction while you play. A static recompilation does that translation once, before you play:
- The game’s ARM64 machine code is translated into C (Ocarina Recomp:
recomp/gen.py; Hookshot: nx2/lift.py).
- That C is compiled together with a runtime that stands in for the console’s system software.
- The game’s NVN 2 graphics calls are rebuilt on Vulkan, and Switch 2 Ampere shaders are lowered and translated to SPIR-V.
The result is an ordinary PC executable, built from your copy. That is why the first install takes a long time, why shaders stutter the first time you enter an area, and why each new release means building again.
What you bring
Your own copy, at the right version
None of the projects includes the game, keys or a finished executable. Each checks the version of the copy you give it and refuses others.
| Project | Supported copy | Input | Setup |
|---|
| Ocarina Recomp | Switch 2 edition, game version 1.1.1 | .nup, or a folder with exefs and romfs | Builds on your PC, 30 min to 2 h |
| Hookshot | Switch 2 edition: program 0400486024DEC000, update v131072, build e0f3ccfa | .nup, or romfs + exefs folders | Builds on your PC, about 40 min |
| TriAevum | Ocarina of Time 3D, EUR or USA (original or Rev 1) | Decrypted .3ds or .cci | Forge prepares shaders, a few minutes |
This site does not explain how to obtain or extract game files. Use a copy you legally own; keep everything the build creates on your own PC.