MagicBeanDev/Hookshot

Archived

Watch

Fork 0

white line in shadow draw distance transition #2168

Closed

opened 2026-11-11 05:49:03 +00:00 by Caliel666 · 3 comments

Caliel666 commented

2026-11-11 05:49:03 +00:00

(Migrated from github.com)

Hookshot version

v2.1.0

What kind of problem

Graphics (missing, black or wrong-coloured things, lighting, flicker)

What happened

https://streamable.com/3itnn0
couldn't upload the video here
a line appears everywhere in the game, even outside shadows around the draw distance

Where in the game

hyrule field, everywhere

How often

Every time

Graphics card and driver version

AMD 9070XT

CPU, RAM and operating system

ryzen 7600, 32gb, windows 11

Changes from the defaults

No response

Other software hooked into the game

No, nothing hooked in

hookshot_log.txt

hookshot_log - Copy (2).txt

Screenshots or video

Before you send it

I'm on the newest release, or the problem is still there on it.
I searched the open issues for this problem.
I'm not attaching game files, keys, hookshot.exe, the .bin caches or saves.

### Hookshot version v2.1.0 ### What kind of problem Graphics (missing, black or wrong-coloured things, lighting, flicker) ### What happened https://streamable.com/3itnn0 couldn't upload the video here a line appears everywhere in the game, even outside shadows around the draw distance ### Where in the game hyrule field, everywhere ### How often Every time ### Graphics card and driver version AMD 9070XT ### CPU, RAM and operating system ryzen 7600, 32gb, windows 11 ### Changes from the defaults _No response_ ### Other software hooked into the game No, nothing hooked in ### hookshot_log.txt [hookshot_log - Copy (2).txt](https://github.com/user-attachments/files/34672418/hookshot_log.-.Copy.2.txt) ### Screenshots or video <img width="1425" height="624" alt="image" src="https://github.com/user-attachments/assets/78da6133-f6c6-4a93-b403-3e3dae8ea87b" /> ### Before you send it - [x] I'm on the newest release, or the problem is still there on it. - [x] I searched the open issues for this problem. - [x] I'm not attaching game files, keys, hookshot.exe, the .bin caches or saves.

👍 1

gatosardina commented

2026-11-11 11:11:42 +00:00

(Migrated from github.com)

Same here, also on 9070XT

PapaiW commented

2026-11-11 15:37:02 +00:00

(Migrated from github.com)

I can reproduce the exact same shadow artifact reported here, and I was able to isolate a reliable trigger on a non-XT RX 9070.

Hardware and software

Hookshot: v2.1.0
GPU: XFX AMD Radeon RX 9070 16 GB (non-XT)
Driver: AMD Adrenalin 26.10.2 WHQL Optional
CPU: AMD Ryzen 5 5600
RAM: 32 GB
OS: Windows 11

Reproduction

In Hookshot's Graphics settings, change Anisotropic Filtering:

Game's: The artifact disappears and shadows look normal.
2x: Artifact appears.
4x: Artifact appears.
8x: Artifact appears.
16x: Artifact appears.

The issue occurs consistently at every forced anisotropic filtering level, not just at 16x.

Additional details

A circular halo/boundary appears around Link in shadowed areas. It moves with the character as he walks, creating a visible boundary in the shadows.

Switching back to Game's immediately removes the artifact.

The AMD Adrenalin driver-level anisotropic filtering override is disabled, so the setting is being controlled exclusively through Hookshot.

Graphics settings

Output resolution: 5120x2880 (5K)
Upscaler: AMD FSR 4
Render resolution: Quality (67%) – 3414x1920
Mesh shaders: Automatic
Anisotropic filtering: 2x / 4x / 8x / 16x (artifact present); Game's (no artifact)

This adds another reproducible data point from an RX 9070 (non-XT), which may help identify an AMD-specific issue involving anisotropic filtering and shadow rendering.

I can provide further testing and comparisons if needed.

hookshot_log.txt

Screenshots

I can reproduce the exact same shadow artifact reported here, and I was able to isolate a reliable trigger on a non-XT RX 9070. ### Hardware and software - **Hookshot:** v2.1.0 - **GPU:** XFX AMD Radeon RX 9070 16 GB (non-XT) - **Driver:** AMD Adrenalin 26.10.2 WHQL Optional - **CPU:** AMD Ryzen 5 5600 - **RAM:** 32 GB - **OS:** Windows 11 ### Reproduction In Hookshot's Graphics settings, change **Anisotropic Filtering**: - **Game's:** The artifact disappears and shadows look normal. - **2x:** Artifact appears. - **4x:** Artifact appears. - **8x:** Artifact appears. - **16x:** Artifact appears. The issue occurs consistently at every forced anisotropic filtering level, not just at 16x. ### Additional details A circular halo/boundary appears around Link in shadowed areas. It moves with the character as he walks, creating a visible boundary in the shadows. Switching back to **Game's** immediately removes the artifact. The AMD Adrenalin driver-level anisotropic filtering override is disabled, so the setting is being controlled exclusively through Hookshot. ### Graphics settings - **Output resolution:** 5120x2880 (5K) - **Upscaler:** AMD FSR 4 - **Render resolution:** Quality (67%) – 3414x1920 - **Mesh shaders:** Automatic - **Anisotropic filtering:** 2x / 4x / 8x / 16x (artifact present); Game's (no artifact) This adds another reproducible data point from an RX 9070 (non-XT), which may help identify an AMD-specific issue involving anisotropic filtering and shadow rendering. I can provide further testing and comparisons if needed. ### [hookshot_log.txt](https://github.com/user-attachments/files/34694458/hookshot_log.txt) ### Screenshots <img width="2560" height="1440" alt="With Anisotropic Filtering" src="https://github.com/user-attachments/assets/f0840222-17fe-4e7a-afb0-ce9f78e47a83" /> <img width="2560" height="1440" alt="Without Anisotropic Filtering" src="https://github.com/user-attachments/assets/1b4ba138-0e28-4373-a1c8-b929682586ac" />

NotRexed commented

2026-11-11 21:25:54 +00:00

(Migrated from github.com)

Thanks for the report. Reports of the same problem are now collected in #2509, which lists this one with your details and links back here, so one fix closes them together and the open list stays readable. Follow #2509 for the fix, and add new details there (or here). If this turns out to be a separate problem it will be reopened.

👍 1

Commenting is not possible because the repository is archived.