Find your guide

Independent port guide.

Troubleshooting · Hookshot

Ocarina of Time Remake PC Troubleshooting

For a black screen or crash, start the launcher in the built game folder, then check your GPU model and graphics support. Match the symptom and hardware before applying the specific workaround.

On this page

Find Your Symptom

Symptom First thing to try Detailed help
StartupBuilder rejects the game versionTry first: Select the supported updated input.Version checkStartupBuilder needs romfs and exefsTry first: Choose their common parent folder.Folder checkStartupBlack screen or immediate crashTry first: Check the launcher, driver and GPU features.StartupStartupAntivirus removed Builder toolsTry first: Check the download, then use Builder Repair.RepairGraphicsAMD blocky textures or sky rectanglesTry first: Try the texture-format workaround if graphics memory is available.AMD texturesGraphicsOlder GPU misses objectsTry first: Update the driver and check GPU drawing-feature support.Missing geometryGraphicsNVIDIA stutters on every startTry first: Set the driver’s prepared-graphics cache, Shader Cache Size, to Unlimited or 10 GB.Shader cacheCrashes During PlayDeck freezes in Kokiri Forest or the Deku TreeTry first: Enable the manual Deck workaround.Deck hangCrashes During PlayTextures degrade during a long sessionTry first: Save/reload or restart, then check quality.Long sessionsAudioA speaker goes silentTry first: Update an older build for the audio fix.AudioControllerController input or prompts are wrongTry first: Connect before launch; check layout and device mode.ControllerControllerMotion aiming driftsTry first: Rest the controller briefly on a table.Gyro driftUpdate or DLCUpdate or build stopsTry first: Check program/input versions and retain the error.Update checksGet HelpA different repeated failureTry first: Keep the scene, settings and failing log.Report checklist

Fixed in newer versions

SymptomFixed inDetailed help
Older guard-house crashUpdate and rebuild; fixed work shipped in v2.1.0.v2.1.0Guard-house fix

Game Won't Start or Shows a Black Screen

Start the built launcher

HookshotWindowsLinux
  1. On Windows, open hookshot.exe in the built game folder; on Linux, open hookshot there.
  2. Check Vulkan 1.3 (the graphics interface) and mesh shaders (the GPU object-drawing feature) on System Requirements.
  3. Update the graphics driver, then match a continuing failure to the GPU-specific report.

Use the installation guide for normal first-launch and menu operations.

AMD or Intel startup failure

HookshotAMDIntelOpen

For AMD device loss—a crash where the graphics device stops responding—update the driver and include your exact card or processor with built-in graphics in the AMD tracker. For Intel black screens or crashes, keep the GPU model, driver and startup log for the Intel tracker. Use the report checklist for a continuing failure.

Wrong game version or missing folders

Error message
The folder <path> needs both a romfs and an exefs folder in it.
Hookshot
  1. Choose the parent directory containing both romfs and exefs.
  2. Check that your input matches program 0400486024DEC000, update v131072 and build prefix e0f3ccfa.
  3. Use Game Files for the build-ID result before starting another build.

Builder tools were removed

HookshotWindowsWorkaround

If antivirus removed build tools, check the original package through Download's source and fingerprint checks. In Windows Builder, look for The build tools need repairing. Click Repair at the bottom right of that error page, beside Back, to download and check the tools again; the button appears for tool failures. Then continue the installation.

Graphics Glitches

AMD blocky textures or sky rectangles

HookshotAMDWorkaround
  1. Close the game and open hookshot_env.txt in the game folder.

  2. Add the documented texture switch on its own line:

    text
    RX_VK_ASTC_RGBA8=1
    
  3. Restart and check the affected scene; remove that line to undo the change.

Leave extra graphics memory available before trying this texture workaround.

If the same corruption continues, attach the scene, GPU/driver and log to the AMD texture report.

Missing objects on older GPUs

HookshotOpen

Older cards without mesh shaders, the GPU feature used to draw game objects, try a substitute graphics path and can miss objects. Update the driver and check the mesh-shader tracker for the GPU and scene. Match hardware requirements before building on another device.

NVIDIA stutters on every start

HookshotWindowsNVIDIAWorkaround
  1. In the NVIDIA driver's Shader Cache Size setting, the space for prepared graphics work, choose Unlimited or 10 GB.
  2. Revisit the affected scene and compare the repeated pause after graphics preparation.
  3. If it still repeats, keep the failing scene and log for the shader-stutter report.

First visits can pause while graphics drawing work is prepared; repeated starts can also be affected by NVIDIA's driver-cache limit.

Use Settings for ordinary quality and frame-generation choices.

Crashes During Play

Deck freezes in Kokiri Forest or the Deku Tree

HookshotSteam DeckWorkaround
  1. Close the game and open hookshot_env.txt in its folder.

  2. Add the exact workaround line:

    text
    RX_VK_MESH_NOCULL=2c56dc1006942f74
    
  3. Restart and check the failing area; remove this added line to undo the change.

If Hookshot freezes in Kokiri Forest or the Great Deku Tree, enable this manual workaround. v2.1.0 includes support for this switch; apply it through the steps below when the freeze occurs.

For a continuing hang, send the build, settings, device details and failing log to the Deck tracker. Device reports and fork defaults belong on Steam Deck.

Textures degrade during a long session

HookshotWorkaround

Save/reload or restart can temporarily clear progressive texture corruption. Lower the quality preset when graphics memory is limited, using the graphics-memory choices. If the problem returns, keep the scene and log for the long-session texture report.

Older guard-house crash

HookshotFixed in v2.1.0

The guard-house crash fix is included in v2.1.0. Update and rebuild the older installation, keeping a save backup first.

Audio Problems

Hookshot

For a speaker going silent on an older build, update for the audio-buffer reporting fix. If the failure continues, include the scene and failing log with the report checklist.

Controller Problems

Controller input or prompts are wrong

HookshotWorkaround
  1. Connect the controller before starting Hookshot.
  2. Check Controls for its reported layout, then compare the default action positions.
  3. If the pad has a mode switch, try the other mode and check the prompts again.
  4. For continuing device-layout problems, include the exact controller in the layout discussion.

Motion aiming drifts

HookshotWorkaround

Rest the gyro controller on a table briefly so Hookshot can learn the drift. Use Controls → Motion for the supported devices and sensitivity settings.

Update or Build Stops

  1. 1
    Check the installed Hookshot version and the supported program, update and build on Game Files.
  2. 2
    In Windows Builder, choose Show details on the build screen or error page. On the error page, Copy for a bug report copies the failure and recent build output.
  3. 3
    In Linux Builder, read the scrolling output below the progress bar and keep the lines around the failure before closing the window.
  4. 4
    For removed tools, use Builder Repair; for the normal in-place rebuild, use Updates.

Builder prepares shaders at the end of building, with first-launch preparation continuing when that stage was skipped or failed. Use Saves for restoring progress or choosing the correct profile after a manual transfer.

How to Get Help

Get the output for the stage that failed before closing Builder or starting another game session.

Failed stage Where to find the output
Windows build or update Builder → Show details; on the error page, Copy for a bug report
Linux build or update Scrolling output below Builder's progress bar
Game started from the launcher hookshot_log.txt in the game folder; older runs are hookshot_log.1.txt through hookshot_log.4.txt
Game started from a terminal The terminal output

For help with a repeated failure, use the matching symptom tracker or Hookshot's issue form. Include your Hookshot and game-input versions, operating system, CPU/GPU and driver, the failing scene and steps, and the output above; add a screenshot if it shows the problem. Check the output for personal information before sharing and keep game files out of the report.