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 helpFixed in newer versions
| Symptom | Fixed in | Detailed help |
|---|---|---|
| Older guard-house crashUpdate and rebuild; fixed work shipped in v2.1.0. | v2.1.0 | Guard-house fix |
Game Won't Start or Shows a Black Screen
Start the built launcher
- On Windows, open
hookshot.exein the built game folder; on Linux, openhookshotthere. - Check Vulkan 1.3 (the graphics interface) and mesh shaders (the GPU object-drawing feature) on System Requirements.
- 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
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
The folder <path> needs both a romfs and an exefs folder in it.- Choose the parent directory containing both
romfsandexefs. - Check that your input matches program
0400486024DEC000, updatev131072and build prefixe0f3ccfa. - Use Game Files for the build-ID result before starting another build.
Builder tools were removed
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
-
Close the game and open
hookshot_env.txtin the game folder. -
Add the documented texture switch on its own line:
RX_VK_ASTC_RGBA8=1 -
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
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
- In the NVIDIA driver's Shader Cache Size setting, the space for prepared graphics work, choose Unlimited or 10 GB.
- Revisit the affected scene and compare the repeated pause after graphics preparation.
- 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
-
Close the game and open
hookshot_env.txtin its folder. -
Add the exact workaround line:
RX_VK_MESH_NOCULL=2c56dc1006942f74 -
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
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
The guard-house crash fix is included in v2.1.0. Update and rebuild the older installation, keeping a save backup first.
Audio Problems
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
- Connect the controller before starting Hookshot.
- Check Controls for its reported layout, then compare the default action positions.
- If the pad has a mode switch, try the other mode and check the prompts again.
- For continuing device-layout problems, include the exact controller in the layout discussion.
Motion aiming drifts
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
- 1Check the installed Hookshot version and the supported program, update and build on Game Files.
- 2In 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.
- 3In Linux Builder, read the scrolling output below the progress bar and keep the lines around the failure before closing the window.
- 4For 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.
Sources
Checked November 13, 2026.
- Hookshot project github.com
- Hookshot v2.1.0 release github.com
- Project feedback github.com
- Hookshot known issues and workarounds github.com
- Builder input checks github.com
Zelda PC Guide