I went through the same thing even in the new update, and it happened when entering the Great Deku Tree #360

Closed

opened 2026-11-07 22:19:34 +00:00 by titissg · 5 comments

titissg commented

2026-11-07 22:19:34 +00:00

(Migrated from github.com)

Builder version

Foliage and lighting, update offer, Linux AppImage, rumble

How you built

Hookshot Builder app (Windows)

Game files given to it

A .nup

The error

When entering the tree, only the start loads and it goes to a blank screen
without sound or anything

Visual Studio or Build Tools version, and Windows SDK version

No response

Operating system and free space on the output drive

windows 11 pro 26H2, 82 gb free

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 Foliage and lighting, update offer, Linux AppImage, rumble ### How you built Hookshot Builder app (Windows) ### Game files given to it A .nup ### The error ```text When entering the tree, only the start loads and it goes to a blank screen without sound or anything ``` ### Visual Studio or Build Tools version, and Windows SDK version _No response_ ### Operating system and free space on the output drive windows 11 pro 26H2, 82 gb free ### 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.

NotRexed commented

2026-11-07 22:20:44 +00:00

(Migrated from github.com)

Thanks. Could you attach hookshot_log.txt (next to hookshot.exe) from a run where this happens, and say which GPU and driver you have? A blank screen with no sound at all is different from the usual black screen with sound after the opening (first-time shader compiling, or the GPU crash in #150), so the log is what tells us which it is. Does the game window still respond, or is it frozen?

Thanks. Could you attach `hookshot_log.txt` (next to `hookshot.exe`) from a run where this happens, and say which GPU and driver you have? A blank screen with no sound at all is different from the usual black screen with sound after the opening (first-time shader compiling, or the GPU crash in #150), so the log is what tells us which it is. Does the game window still respond, or is it frozen?

titissg commented

2026-11-07 22:32:24 +00:00

(Migrated from github.com)

hookshot_log.txt
RX 6650xt 32.0.21045.16010.
The window never responded

[hookshot_log.txt](https://github.com/user-attachments/files/34529812/hookshot_log.txt) RX 6650xt 32.0.21045.16010. The window never responded

NotRexed commented

2026-11-08 00:04:47 +00:00

(Migrated from github.com)

One thing that stands out across the AMD logs here and in #121, #148, #150, #224, #229, #370: on AMD driver version 0x800161 two of the game's pipelines (5fa56485a6b07619, 6eaa646d07ea4e43) are rejected by the driver ('not made (-13)'), and in your log the window hangs right after that. On the newer driver 0x8001a0 they build fine in every log. If you can, please update to the latest AMD Adrenalin driver and try again, and attach hookshot_log.txt either way.

titissg commented

2026-11-08 00:22:22 +00:00

(Migrated from github.com)

now it stays black with audio (I updated the driver)

hookshot_log.txt

now it stays black with audio (I updated the driver) [hookshot_log.txt](https://github.com/user-attachments/files/34531224/hookshot_log.txt)

NotRexed commented

2026-11-09 05:47:11 +00:00

(Migrated from github.com)

Tracked in #996, follow there. That issue collects every report of AMD driver crashes, device lost and freezes on Windows, 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.