Find your guide

Independent port guide.

Updates · Hookshot

Ocarina of Time Remake PC Port Updates and Progress

Back up your saves and settings, then choose Update beside Play in Hookshot's built launcher. The updater rebuilds in the existing folder and keeps your user data; it reuses prepared code so only changed parts need compiling again.

On this page

How to Update Safely

Close the game and follow the save, settings and mods backup checklist. Stable updates preserve saves, hookshot_options.ini, hookshot_env.txt and mods. Choose the system you use for the launcher steps.

Windows

  1. 1
    Open hookshot.exe in the built game directory.
  2. 2
    Choose Update beside Play.
  3. 3
    Allow changed components to download and rebuild in the existing directory, then use the launcher to play.

The update refreshes the launcher, the graphics-drawing component and the built game. Keep the cached build work so the next update can reuse it.

Linux

  1. 1
    Open hookshot in the built game directory.
  2. 2
    Keep the Builder AppImage available and choose Update beside Play.
  3. 3
    Let changed components download and rebuild in place, then launch the prepared game.

The Linux launcher uses the AppImage during updates, so keep it after the initial installation. Builder keeps reusable parts of the current build and removes older temporary work.

Hookshot Release Changes

  • Improves gyro aiming and audio output/menu behavior.
  • Improves NVIDIA image reconstruction and edge smoothing, and Linux graphics.
  • Prepares shaders at the end of building, with first-launch preparation continuing when that work was skipped or failed.
  • Supports a manual Steam Deck workaround for Kokiri Forest or Great Deku Tree freezes; enable its switch if those freezes occur.

Open the full release notes for the selected program release. Use Troubleshooting for the action on a specific symptom, including the guard-house crash fix and remaining hardware-specific failures.

For playable areas and project choices, use Ports.

Formal Release or Development Build?

Use the regular release linked in the header for this guide. Development builds are unfinished versions of ongoing work and can break saves or settings; back up before switching to one. Download identifies the program package for a fresh installation, while Saves owns the backup and restoration instructions.

Go Back After an Update Problem

  1. 1
    Close the game and back up your saves and settings. Keep the current game folder while preparing the replacement.
  2. 2
    Open Hookshot's GitHub Releases, find the previous regular release you want and copy its exact release label, called a tag.
  3. 3
    On Windows, save the Builder from Download, open PowerShell in its download folder and run the commands below. Paste that label when prompted; --tag tells Builder which release to use. Opening Builder normally selects the latest release.
powershell
$releaseTag = Read-Host "Paste the previous release tag"
.\HookshotBuilder.exe --tag $releaseTag
  1. On Linux, choose the AppImage from that older release's Assets, allow it to run and open it.
  2. Build into a different game folder, using your original supported .nup or romfs and exefs input, then follow Saves to restore your backed-up profile.

A normal in-place Update reuses the game input retained in the installation, so it does not need the original .nup again. If the retained files are missing, select the original input again; a fresh build in a separate folder also needs it.

For an update or build that stops, use How to Get Help for the error output and log locations.