New feedback in the last version on the specs: Ryzen 5 5600X & AMD Radeon 6700XT #596

Closed

opened 2026-11-08 13:47:12 +00:00 by LlaviLlava · 4 comments

LlaviLlava commented

2026-11-08 13:47:12 +00:00

(Migrated from github.com)

Builder version

Ultrawide, AMD black-screen fix, fewer shader stalls, less flicker

How you built

Hookshot Builder app (Windows)

Game files given to it

A .nup

The error

Good news today!

I've updated Hookshot to the latest version, and I've finally managed to get past the initial sequence and reach the actual gameplay. I can now move Link around!

The first issues I've noticed are:

- Link's character model doesn't render correctly during the cutscene. His body appears unusually bright, as if it were being over-illuminated.
- There are still some lighting issues in certain areas.
- When entering Kokiri Forest, I notice widespread texture flickering. It doesn't happen constantly, but it occurs most of the time.

Regarding performance, I'm getting over 100 FPS with frame generation enabled. However, the actual in-game frame rate is around 30–40 FPS, with occasional peaks close to 50 FPS.

Overall, I'm really happy with the progress being made. It's great to see these improvements, especially on AMD GPUs. I believe it's only a matter of time before the game becomes even more stable and the remaining AMD-specific issues are ironed out.

Thanks for all the hard work!

Visual Studio or Build Tools version, and Windows SDK version

No response

Operating system and free space on the output drive

Windows 11 26H2 free space in E: 414 GB

Before you send it

I'm on the newest release, or it still fails on it.
I searched the open issues for this error.
I'm not attaching game files or anything built from them.

### Builder version Ultrawide, AMD black-screen fix, fewer shader stalls, less flicker ### How you built Hookshot Builder app (Windows) ### Game files given to it A .nup ### The error ```text Good news today! I've updated Hookshot to the latest version, and I've finally managed to get past the initial sequence and reach the actual gameplay. I can now move Link around! The first issues I've noticed are: - Link's character model doesn't render correctly during the cutscene. His body appears unusually bright, as if it were being over-illuminated. - There are still some lighting issues in certain areas. - When entering Kokiri Forest, I notice widespread texture flickering. It doesn't happen constantly, but it occurs most of the time. Regarding performance, I'm getting over 100 FPS with frame generation enabled. However, the actual in-game frame rate is around 30–40 FPS, with occasional peaks close to 50 FPS. Overall, I'm really happy with the progress being made. It's great to see these improvements, especially on AMD GPUs. I believe it's only a matter of time before the game becomes even more stable and the remaining AMD-specific issues are ironed out. Thanks for all the hard work! ``` ### Visual Studio or Build Tools version, and Windows SDK version _No response_ ### Operating system and free space on the output drive Windows 11 26H2 free space in E: 414 GB ### Before you send it - [x] I'm on the newest release, or it still fails on it. - [x] I searched the open issues for this error. - [x] I'm not attaching game files or anything built from them.

LlaviLlava commented

2026-11-08 14:01:20 +00:00

(Migrated from github.com)

Little update: When im trying to open again the game, get stuck compilating the 2 last shaders of 4985, and i remember another problem with the audio, get desync sometimes in cinematics

LlaviLlava commented

2026-11-08 16:33:09 +00:00

(Migrated from github.com)

Another update. I was testing in the Kokiri Forest and at some point my AMD drivers crashed. The screen got black without signal and I had to restart the PC. My current driver's version is 26.10.1

FabianVazquez-Mex commented

2026-11-08 19:48:20 +00:00

(Migrated from github.com)

Same here on an AMD Radeon RX 6700 XT, v2.0.2 (driver: 26.10.1).

After the first cutscene the screen stayed black for a long time, but
it eventually continued to gameplay once "Preparing shaders" had
finished (95955 shaders).
In Hyrule Field, the castle and town in the distance first rendered as
flat white silhouettes, then rendered correctly after a while (same
spot). Screenshots attached.
Grid-like lines on the grass that persist after shaders load. Not sure
if it's a bug.
~66-68 fps shown, "game" ~32-34 [frame generation on/off].

No game files attached.

Same here on an AMD Radeon RX 6700 XT, v2.0.2 (driver: 26.10.1). - After the first cutscene the screen stayed black for a long time, but it eventually continued to gameplay once "Preparing shaders" had finished (95955 shaders). - In Hyrule Field, the castle and town in the distance first rendered as flat white silhouettes, then rendered correctly after a while (same spot). Screenshots attached. - Grid-like lines on the grass that persist after shaders load. Not sure if it's a bug. - ~66-68 fps shown, "game" ~32-34 [frame generation on/off]. No game files attached.

NotRexed commented

2026-11-09 05:50:31 +00:00

(Migrated from github.com)

Tracked in #1006, follow there. That issue collects every report of AMD-specific rendering problems, and this one is linked from it with its GPU, version and log details. If it still happens on v2.0.6 (https://github.com/NotRexed/Hookshot/releases/tag/v2.0.6; Update next to Play in the launcher), please add a comment there with your hookshot_log.txt.

Commenting is not possible because the repository is archived.