AMD RX 6750 XT, 2.1.0: white line artifacts (grass and mountain outline) and low fps in open areas #2444

Closed
opened 2026-11-11 19:25:35 +00:00 by NicoCancedda · 2 comments
NicoCancedda commented 2026-11-11 19:25:35 +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

This is a different problem from my earlier issue, so I'm opening a new one.

Setup: Hookshot 2.1.0, AMD Radeon RX 6750 XT 12 GB (Adrenalin 26.10.1), Intel i7-11700F, 32 GB RAM, Windows 11.
Settings: 1440p, no upscaling, upscaler set to the game's own, frame generation x2, no frame pacing.

Visual artifacts (two screenshots attached, the blue arrow points at each one):

  1. A thin white line that crosses the grass on the hill near Hyrule Field. It looks like a beam of light.
  2. A dotted, bright outline that follows the mountain ridges against the sky in Hyrule Field.
    They look like two different things to me. I don't know if they come from frame generation or from the renderer itself. I can test with frame generation off and compare if that helps.

Performance:

  • In small areas like Goron City the game runs at a rock-solid 60 fps.
  • In Hyrule Field, Kokiri Forest and Kakariko Village the fps drop a lot, but they are stable and the game is playable.
  • In the overlay screenshots I see for example "64 FPS" with "game 32" and "62 FPS" with "game 30". If I read it correctly, the game itself runs at about 30-32 fps in the open areas and frame generation x2 doubles it to about 60-64.

I'm happy to test anything on AMD and send more information

Where in the game

Hyrule Field

How often

Every time

Graphics card and driver version

RX 6750 XT 12 GB (Adrenalin 26.10.1)

CPU, RAM and operating system

Intel i7-11700F, 32 GB RAM, Windows 11

Changes from the defaults

Settings: 1440p, no upscaling, upscaler set to the game's own, frame generation x2, no frame pacing.

Other software hooked into the game

No, nothing hooked in

hookshot_log.txt

hookshot_log.txt

Screenshots or video

Screenshot 2026-11-11 201424 Screenshot 2026-11-11 201433

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 This is a different problem from my earlier issue, so I'm opening a new one. Setup: Hookshot 2.1.0, AMD Radeon RX 6750 XT 12 GB (Adrenalin 26.10.1), Intel i7-11700F, 32 GB RAM, Windows 11. Settings: 1440p, no upscaling, upscaler set to the game's own, frame generation x2, no frame pacing. Visual artifacts (two screenshots attached, the blue arrow points at each one): 1. A thin white line that crosses the grass on the hill near Hyrule Field. It looks like a beam of light. 2. A dotted, bright outline that follows the mountain ridges against the sky in Hyrule Field. They look like two different things to me. I don't know if they come from frame generation or from the renderer itself. I can test with frame generation off and compare if that helps. Performance: - In small areas like Goron City the game runs at a rock-solid 60 fps. - In Hyrule Field, Kokiri Forest and Kakariko Village the fps drop a lot, but they are stable and the game is playable. - In the overlay screenshots I see for example "64 FPS" with "game 32" and "62 FPS" with "game 30". If I read it correctly, the game itself runs at about 30-32 fps in the open areas and frame generation x2 doubles it to about 60-64. I'm happy to test anything on AMD and send more information ### Where in the game Hyrule Field ### How often Every time ### Graphics card and driver version RX 6750 XT 12 GB (Adrenalin 26.10.1) ### CPU, RAM and operating system Intel i7-11700F, 32 GB RAM, Windows 11 ### Changes from the defaults Settings: 1440p, no upscaling, upscaler set to the game's own, frame generation x2, no frame pacing. ### Other software hooked into the game No, nothing hooked in ### hookshot_log.txt [hookshot_log.txt](https://github.com/user-attachments/files/34702308/hookshot_log.txt) ### Screenshots or video <img width="2559" height="1439" alt="Screenshot 2026-11-11 201424" src="https://github.com/user-attachments/assets/8d2ea518-f9f5-4c53-9190-fc6a0d999c40" /> <img width="2559" height="1439" alt="Screenshot 2026-11-11 201433" src="https://github.com/user-attachments/assets/f6bbb0f3-e368-45ca-b5c2-ad7ea8e5b2d9" /> ### 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.
NicoCancedda commented 2026-11-11 20:06:48 +00:00 (Migrated from github.com)

Update: after restarting the game, both white lines (the one on the grass and the dotted outline on the mountains) are gone. Before the restart VRAM usage was 11.8 of 12 GB, right after the restart it is about 9.8 GB. So they seem to depend on the state of the session and may be related to VRAM pressure. I think the game may also have been spilling into shared GPU memory before, and I saw a disk usage spike that could be the page file, but I'm not sure about that. I'll keep playing and report if the lines come back when VRAM gets close to full again.

Update: after restarting the game, both white lines (the one on the grass and the dotted outline on the mountains) are gone. Before the restart VRAM usage was 11.8 of 12 GB, right after the restart it is about 9.8 GB. So they seem to depend on the state of the session and may be related to VRAM pressure. I think the game may also have been spilling into shared GPU memory before, and I saw a disk usage spike that could be the page file, but I'm not sure about that. I'll keep playing and report if the lines come back when VRAM gets close to full again.
NotRexed commented 2026-11-11 21:30:35 +00:00 (Migrated from github.com)

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

Thanks for the report. Reports of the same problem are now collected in #1006, which lists this one with your details and links back here, so one fix closes them together and the open list stays readable. Follow #1006 for the fix, and add new details there (or here). If this turns out to be a separate problem it will be reopened.
Commenting is not possible because the repository is archived.
No milestone
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Hookshot#2444
No description provided.