HOOKSHOT GITHUB

The picture is wrong, not gone

Hookshot graphics glitches

A glitch here means the window stays open and the image is distorted. A black window or a hard exit belongs on the other two pages.

Comparison frame showing a Hookshot scene
Second comparison frame from 11 Nov 2026

Field shadows and AMD textures

Issue 468 tracks striped shadows across Hyrule Field and includes a short recording on the issue itself. I link the issue rather than rehosting that clip, because GitHub attachments move. AMD block textures, a sky that turns into a solid rectangle, and a courtyard that goes unusually dark are issues 57 and 1006. The variable those threads share is RX_VK_ASTC_RGBA8=1. It stores the textures as a heavier format, so video memory use goes up and the frame can stall. I would try it only after the driver is current, and I would turn it off if the stall is worse than the blocks.

Stutter, old cards, handheld HUD

The first time you enter a new area, shaders compile and the frame time jumps. The readme calls that expected, and the second visit is the one to judge. If an NVIDIA card stutters on every launch after shaders were already prepared, the same note points at the driver shader cache size and suggests Unlimited or 10 GB.

Cards without mesh shaders, in issue 1001, lose terrain and the cartoon outline, pick up color noise, and sit around 0 to 10 fps. That is a capability gap, not a sharpness slider. Handheld AMD reports add a stretched button prompt for one frame, a flickering map, missing hearts in issues 739 and 798, and orange polygon spikes in issue 837. Issue 151 describes water flickering once video memory is full. Those are separate from the Hyrule Field stripes, so I do not offer one switch for all of them.

Questions

The stripes are only in Hyrule Field. Is that the AMD texture bug?

Issue 468 is the stripe report. Issues 57 and 1006 are the blocky textures. They are different threads.

Should I set RX_VK_ASTC_RGBA8 on an NVIDIA card?

The threads that name it are AMD texture reports. I do not have a published NVIDIA result for that variable.

Sources

Public references and check dates
SourceEvidence statusChecked
Issue 468 1 reference · shared publishers and mirrors count together 2026-11-11
Issue 1006 1 reference · shared publishers and mirrors count together 2026-11-11
Issue 1001 1 reference · shared publishers and mirrors count together 2026-11-11
Readme 1 reference · shared publishers and mirrors count together 2026-11-11

How we check pages

Related