Common issues and answers
These are examples from maintainer responses to reports, mostly about v2.0.14, collected on November 10, 2026. They describe what was reported and suggested at that time. Use the linked trackers for current status and advice. This page does not maintain a separate list of open or fixed bugs. A report closed as a duplicate is not evidence of a fix.
Quick lookup
Section titled “Quick lookup”The build says a compressed file ends before its frame completes
Section titled “The build says a compressed file ends before its frame completes”In the response to #1996, the maintainer traced the error to an incomplete game copy and recommended copying or dumping it again. The file size mentioned in that report applies to that particular copy, not every supported input.
NVIDIA’s DLSS SDK could not be downloaded
Section titled “NVIDIA’s DLSS SDK could not be downloaded”The response to #1962 identified a connection reset during download. The suggested options were retrying later or building without optional DLSS. Use the thread for subsequent advice if the error persists.
The builder stays at reading game files
Section titled “The builder stays at reading game files”The v2.0.14 report #1988 was redirected to #1876. Follow that tracker and include the exact stage, build, and builder output if adding a report.
The game closes immediately after Play
Section titled “The game closes immediately after Play”The response to #2004 pointed to #1288. Check that thread for current troubleshooting steps. Include your OS, GPU, driver, build, and log when reporting the symptom.
Gohma walks into a wall or stops attacking
Section titled “Gohma walks into a wall or stops attacking”The response to #1927 recommended a 60 FPS game cap for the reported fight behavior. The explanation in #1742 described timers above 60 FPS. Check #1742 and the current menu guidance before applying that advice to a newer build.
The HUD ghosts or shimmers with frame generation
Section titled “The HUD ghosts or shimmers with frame generation”For v2.0.14, the response to #1976 pointed to #1635 and suggested changing frame pacing or the frame-generation multiplier. An earlier response narrowed a case to 2× frame generation with pacing on.
Results differed between reports. The reporter in #1953 said a restart helped temporarily before shimmering returned in another area. Read the tracker for current settings and fixes rather than treating one report’s result as a general solution.
FPS stays low after changing areas
Section titled “FPS stays low after changing areas”The response to #2023 redirected the report to #1400. Use the README’s performance-reporting instructions and record which transitions trigger the drop.
Dungeon walls or blocks are invisible on an older GPU
Section titled “Dungeon walls or blocks are invisible on an older GPU”The response to #1900 connected missing geometry on a GTX 1050 Ti to its lack of mesh shaders and pointed to #1001. That tracker covers subsequent fallback work and reports.
Steam Deck freezes or has missing dungeon geometry
Section titled “Steam Deck freezes or has missing dungeon geometry”The v2.0.14 Steam Deck OLED report #1956 was redirected to #1000. Follow it for current Linux/Steam Deck advice. AMD-on-Windows reports have a separate tracker, #996.
Controller buttons do not match the selected layout
Section titled “Controller buttons do not match the selected layout”The response to #1923 pointed to #1655 for play and ocarina controls disagreeing with the selected layout. Include the controller, Hookshot bindings, and the game’s own control settings if adding a report.
Textures look low resolution or corrupted on AMD
Section titled “Textures look low resolution or corrupted on AMD”The RX 9060 XT report #1986 was redirected to #1006. Check that tracker and the README’s texture-workaround guidance for current advice and tradeoffs.