How to Install Ocarina of Time Remake on PC
Open Hookshot Builder, select your own supported game input and destination, then build the PC program and choose Play. Builder downloads its tools and prepares the game locally; all code preparation happens through the setup.
On this page
Before You Start
- Game: your own Switch 2 remake, update
v131072, build prefixe0f3ccfa, supplied as a.nuppackage orromfsandexefsfolders; check the input. - Computer: Windows 10/11 x64 or Linux x86-64 with glibc 2.35+ (a core system library), Vulkan 1.3 (the graphics interface) and mesh shaders (a feature for drawing game objects); the Linux AppImage also needs AVX2 (CPU instructions); check your hardware.
- Memory and disk: at least 16 GB RAM and around 60 GB free while building, preferably on an SSD.
- Program and internet: get the Builder for your system and keep internet available for its tool downloads.
Choose one system tab and follow its steps to the ready screen, then launch the prepared game.
Install on Windows
1 Get the Windows Builder
Save HookshotBuilder.exe from the Hookshot release for Windows 10 or 11 x64. Use the Builder application for this installation; the Windows-x64 ZIP serves the separate RecompLauncher launcher.
2 Open Builder
Run the downloaded Builder and let it download and check the tools it needs. The standard setup brings its compiler, the tool that turns the prepared code into a PC program.
3 Select your game input
Choose your supported .nup, or the prepared romfs and exefs folders. For the folder route, select the game parent containing both folders, with the game executable at exefs/main; Builder checks its version before building.
4 Choose the destination and language
Select a writable game folder; the default is Games\Hookshot inside your Windows user folder. Choose Game language for the game text before starting the build.
5 Build the game and prepare shaders
Choose Build the game and let Builder translate and compile the input into the PC game. Shader preparation runs at the end of building; shaders are the graphics programs needed to draw the scenes.
Preparation can continue on the first game launch if shader preparation was skipped or failed during the build. Keep the selected game folder and Builder workspace available for this process; both use disk space while the game is being prepared.
6 Choose Play
When Builder displays Your game is ready, choose Play. To launch again later, open hookshot.exe inside the game folder and choose Play from that launcher.
Install on Linux
1 Get the x86-64 AppImage
Save Hookshot-v2.1.0-x86_64.AppImage from the Hookshot release; the AppImage packages Builder as one Linux application file. Use a CPU with the AVX2 instructions and glibc 2.35 or newer, the Linux system library, with the required Vulkan graphics features.
2 Allow the AppImage to run
Enable executable permission in the file's properties, or open a terminal in its download directory and run:
chmod +x "Hookshot-v2.1.0-x86_64.AppImage"
Open the AppImage to start Builder.
3 Select your game input
Choose your supported .nup, or the prepared game folder containing romfs and exefs. Builder checks the executable's build ID against the supported e0f3ccfa prefix.
4 Choose the destination and language
Choose a writable output folder; the default is ~/Games/Hookshot. Select Game language for this installation, then continue to the build.
5 Build and finish preparation
Let Builder download its tools and prepare the game locally, including shader preparation at the end of building. If that graphics preparation was skipped or failed, the game continues it at first launch.
6 Choose Play and keep the AppImage
Choose Play when Your game is ready appears; later, open hookshot in your selected game folder. Keep the AppImage because the built launcher uses it for updates. On Steam Deck, return to Add the Mainline Game to Steam after reaching Play.
After Installing
Launch the prepared game
The launcher inside the built game folder provides Play and Update. On Windows it is hookshot.exe; on Linux it is hookshot.
Open the in-game settings menu and start playing
Set a starting point for the first session
- Keep Game frame rate cap at 60, Frame generation at Off and Game speed at Real time for the starting settings. Real time keeps the game at normal speed when performance falls below 60 FPS, down to 15 FPS.
- Use WASD to move and the arrow keys or IJKL to move the camera with the default keyboard layout.
- Let any remaining shader preparation finish at first launch; later visits and starts can reuse cached graphics work. First visits to a scene can still pause while new graphics work is prepared.
Find Builder's workspace
Builder keeps its working files in %LOCALAPPDATA%\HookshotBuilder on Windows (%LOCALAPPDATA% means your account's local application-data folder) and ~/.cache/hookshot-builder on Linux (~ means your home folder), separately from your chosen game directory. Allow space for both the working files and the output game during preparation.
If Setup Stops
- 1Identify whether the stop occurred during tool setup, game-code building or shader preparation, then open the Builder output and keep the error.
- 2For a version rejection, reselect input matching the supported game build.
- 3For a folder error, select the parent containing both
romfsandexefs. - 4For a Linux launch failure, check your graphics driver and the required graphics features against startup troubleshooting.
Free Up Space After Installing
Keep the built game, saves and settings; on Linux, also keep the AppImage used for updates. Let Builder handle the temporary build files: it removes older temporary work and keeps reusable parts for later updates.
Sources
Checked November 13, 2026.
- Hookshot project github.com
- Hookshot v2.1.0 release github.com
- Project feedback github.com
- Hookshot Windows and Linux installation github.com
- Builder preparation and cache handling github.com
Zelda PC Guide