How Hookshot Works: Static Recompilation & Vulkan

The local compilation pipeline

1. 1

   nx2/lift.py translates the game’s ARM64 code into C.

2. 2

   nx2/build.py compiles that C with host/, which implements the console system behavior the game expects.

3. 3

   host/nvn_native.c records NVN2 graphics calls; gpu/vk/ replays them through Vulkan.

4. 4

   Switch 2 Ampere shaders are lowered to Maxwell and translated to SPIR-V using Eden’s shader recompiler.

What native means here

The result is a Windows or Linux program compiled ahead of time. The project describes this as static recompilation, rather than a traditional emulator running arbitrary console software.

A native executable still needs the reimplemented system layer, translated shaders, your game assets and compatible host graphics hardware. Native does not mean no translation, no bugs or universal device support.

Why only one game build is supported

The generated code and supporting assumptions target the documented executable build. Another update changes the input, so a matching title alone cannot establish compatibility.

Builder performs the validation and compilation locally from your game. The repository contains tools and source, not a ready-made game executable, game assets or keys. Generated game-derived content must stay on your computer.

Experimental implementation and deeper reading

Rendering, system behavior and shader handling are still being improved. Area-specific bugs, first-visit shader stutter and differing GPU-driver behavior remain possible even after a successful build.

The official development and design documents describe the architecture in greater detail. They are for contributors; ordinary players should follow the Windows or Linux Builder guide instead of assembling a source toolchain.