Game turns into BlackScreen when the deku tree cinematic begins, game audio still working

mb-kt commented

2026-11-07 20:07:34 +00:00

(Migrated from github.com)

Builder version

sha256:b90d57ffdcb563c1cb2376422fbf3fcfdff90c5af6a8aa380d37351db31f0ded

How you built

Hookshot Builder app (Windows)

Game files given to it

A .nup

The error

Game runs well until links awake and the deku tree cinematic begins, Game still runing but blackscreen and cannot move, FPS freezing running on i5 12400F and RTX 5050. FPS Turns around 120 with FG x2 on but falls to 10-20 and this happens even with fg off. controls and audio working but I can't see anything because de black screen

Visual Studio or Build Tools version, and Windows SDK version

Visual Studio Locator version 3.1.7+f39851e70f [query version 4.12.26.35335], Windows SDK 10.0.26100.0

Operating system and free space on the output drive

Win11 Pro 25H2

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 sha256:b90d57ffdcb563c1cb2376422fbf3fcfdff90c5af6a8aa380d37351db31f0ded ### How you built Hookshot Builder app (Windows) ### Game files given to it A .nup ### The error ```text Game runs well until links awake and the deku tree cinematic begins, Game still runing but blackscreen and cannot move, FPS freezing running on i5 12400F and RTX 5050. FPS Turns around 120 with FG x2 on but falls to 10-20 and this happens even with fg off. controls and audio working but I can't see anything because de black screen ``` ### Visual Studio or Build Tools version, and Windows SDK version Visual Studio Locator version 3.1.7+f39851e70f [query version 4.12.26.35335], Windows SDK 10.0.26100.0 ### Operating system and free space on the output drive Win11 Pro 25H2 ### 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.

aerodevxp commented

2026-11-07 20:18:21 +00:00

(Migrated from github.com)

same issue on Linux with the native build: Z1 Extreme + RX 6800

powmcr commented

2026-11-07 20:19:59 +00:00

(Migrated from github.com)

same here ryzen 5 5600 1060 6gb windows 11

AliHMohammad commented

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

(Migrated from github.com)

I had the same black screen after the initial cutscene where he wakes up. I waited +1 min before the game continued. Did you give it a couple of minutes?

Ryzen 78003xd, RTX 5070ti Windows 11

I had the same black screen after the initial cutscene where he wakes up. I waited +1 min before the game continued. Did you give it a couple of minutes? Ryzen 78003xd, RTX 5070ti Windows 11

aerodevxp commented

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

(Migrated from github.com)

I had the same black screen after the initial cutscene where he wakes up. I waited +1 min before the game continued. Did you give it a couple of minutes?

Ryzen 78003xd, RTX 5070ti Windows 11

worth a shot, thanks

> I had the same black screen after the initial cutscene where he wakes up. I waited +1 min before the game continued. Did you give it a couple of minutes? > > Ryzen 78003xd, RTX 5070ti Windows 11 worth a shot, thanks

NotRexed commented

2026-11-07 20:24:34 +00:00

(Migrated from github.com)

Thanks. A black screen with sound when the Deku Tree scene begins is the GPU crash tracked in #150 (device lost in a culling shader while the scene loads). If you can, attach hookshot_log.txt (beside hookshot.exe) there; relaunching usually gets past it.

Thanks. A black screen with sound when the Deku Tree scene begins is the GPU crash tracked in #150 (device lost in a culling shader while the scene loads). If you can, attach `hookshot_log.txt` (beside `hookshot.exe`) there; relaunching usually gets past it.

powmcr commented

2026-11-07 20:36:24 +00:00

(Migrated from github.com)

hookshot_log.txt
ryzen 5 5600 gtx 1060 6gb

[hookshot_log.txt](https://github.com/user-attachments/files/34528312/hookshot_log.txt) ryzen 5 5600 gtx 1060 6gb

aerodevxp commented

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

(Migrated from github.com)

The entire system crashes for me if I wait. Most likely the same issue. Though I can't find any logs files?

The entire system crashes for me if I wait. Most likely the same issue. Though I can't find any logs files? <img width="2102" height="135" alt="Image" src="https://github.com/user-attachments/assets/9428289c-48d8-4a2f-9070-08be0a711992" />

mb-kt commented

2026-11-07 20:45:25 +00:00

(Migrated from github.com)

idk how but y restart the game and loaded well, y tryied turning frametime to real time but I don't thinm that fixed it, I tweak the upscaling but I think same... that's because I write idk how it solved itself I guess but, framerate is bad, I'm staying just moving the camera around and it drops and never keep like 20 or 30, is like 70 then 30 then 50 then 24 then 100 and hopefully I wish it solves playing more but it doesnt' feels like that

haaris7786 commented

2026-11-07 21:13:53 +00:00

(Migrated from github.com)

Same problem for me the intro sequence plays out beautifully then it goes to black I am on then latest version and I am using a Xbox ally X Z2E with 24 gigs of ram and on turbo mode

hookshot_log.txt

Same problem for me the intro sequence plays out beautifully then it goes to black I am on then latest version and I am using a Xbox ally X Z2E with 24 gigs of ram and on turbo mode [hookshot_log.txt](https://github.com/user-attachments/files/34528892/hookshot_log.txt)

EliasCoptere commented

2026-11-07 21:19:37 +00:00

(Migrated from github.com)

same issue for me
hookshot_log.txt

Thanks. A black screen with sound when the Deku Tree scene begins is the GPU crash tracked in #150 (device lost in a culling shader while the scene loads). If you can, attach hookshot_log.txt (beside hookshot.exe) there; relaunching usually gets past it.

same issue for me [hookshot_log.txt](https://github.com/user-attachments/files/34528967/hookshot_log.txt) > Thanks. A black screen with sound when the Deku Tree scene begins is the GPU crash tracked in [#150](https://git.magicbean.dev/MagicBeanDev/Hookshot/issues/150) (device lost in a culling shader while the scene loads). If you can, attach `hookshot_log.txt` (beside `hookshot.exe`) there; relaunching usually gets past it.

danpan1113 commented

2026-11-07 21:55:45 +00:00

(Migrated from github.com)

Same issue. As soon as Link wakes up from the dream and the title logo appears it goes to black screen, I can still hear audio from cut scene and I can hear Link running around if I mash the buttons.

[hos Presentation Thread] vk: submit 69274 failed (-4)
[hos Presentation Thread] vk: device lost: reading the checkpoints
[hos Presentation Thread] vk: device lost: 0 checkpoints (124810 markers set)
[hos Presentation Thread] vk: submit 69274 failed (-4)

This may be relevant, i had the (-4) on totk recomp and updating drivers fixed it back then.

edit: I turned resolution down to 50% and loaded the save file it made during black screen and its working now, i restarted with new game and the deku cutscene plays fine now, dont know if some shaders just happened to be built or if the 50% fixed it or if just coincindence.

Same issue. As soon as Link wakes up from the dream and the title logo appears it goes to black screen, I can still hear audio from cut scene and I can hear Link running around if I mash the buttons. [hos Presentation Thread] vk: submit 69274 failed (-4) [hos Presentation Thread] vk: device lost: reading the checkpoints [hos Presentation Thread] vk: device lost: 0 checkpoints (124810 markers set) [hos Presentation Thread] vk: submit 69274 failed (-4) This may be relevant, i had the (-4) on totk recomp and updating drivers fixed it back then. edit: I turned resolution down to 50% and loaded the save file it made during black screen and its working now, i restarted with new game and the deku cutscene plays fine now, dont know if some shaders just happened to be built or if the 50% fixed it or if just coincindence.

NotRexed commented

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

(Migrated from github.com)

I went through the logs posted here since my last reply:

RTX 2060 log, and the lines quoted for the black screen when Link wakes up: submit ... failed (-4) and device lost (in compute 53caac5f38279735). That's the GPU crash in #150; relaunching usually gets past it, and a driver update is worth a try.
Radeon 890M (Ally X) log: no device lost, but submits of several seconds (up to 44 s) while the game compiles shaders it meets for the first time. That black screen carries on by itself after a minute or two and is shorter on later runs.
GTX 1060 log: it ends while the intro movie is still playing, so it doesn't reach the black screen; please attach one taken after it. This card has no Vulkan mesh shaders, see #148.

I went through the logs posted here since my last reply: - RTX 2060 log, and the lines quoted for the black screen when Link wakes up: `submit ... failed (-4)` and `device lost` (in compute `53caac5f38279735`). That's the GPU crash in #150; relaunching usually gets past it, and a driver update is worth a try. - Radeon 890M (Ally X) log: no device lost, but submits of several seconds (up to 44 s) while the game compiles shaders it meets for the first time. That black screen carries on by itself after a minute or two and is shorter on later runs. - GTX 1060 log: it ends while the intro movie is still playing, so it doesn't reach the black screen; please attach one taken after it. This card has no Vulkan mesh shaders, see #148.

NotRexed commented

2026-11-08 08:21:44 +00:00

(Migrated from github.com)

Release https://github.com/NotRexed/Hookshot/releases/tag/ultrawide should fix this: compute shaders now compile in the background instead of freezing the game (AMD took 15-23 s for one, with a black screen meanwhile), twice as many shaders are prepared before the first start, and on AMD the foliage culling shaders are built without the driver optimizer that hung RX 6600-class cards. Please update (run HookshotBuilder.exe, or accept the game's update offer) and tell me if it still happens, with hookshot_log.txt (and hookshot_log.1.txt if you restarted after a crash).

haaris7786 commented

2026-11-08 09:34:58 +00:00

(Migrated from github.com)

I have tried ultrawide on the Xbox ally x and mostly the same issue but this time I waited a bit and the deku tree sequence started but there was no image I will try again on the newest update

hookshot_log.txt

I have tried ultrawide on the Xbox ally x and mostly the same issue but this time I waited a bit and the deku tree sequence started but there was no image I will try again on the newest update [hookshot_log.txt](https://github.com/user-attachments/files/34540894/hookshot_log.txt)

NotRexed commented

2026-11-08 12:43:53 +00:00

(Migrated from github.com)

Release https://github.com/NotRexed/Hookshot/releases/tag/fast-updates no longer gives back memory the GPU used, on Windows (it was meant for a Linux AMD driver; fuxau traced the Arc device lost to it in #17, and the AMD logs show device lost right after it). If you had device lost, could you try this release and tell us? On Linux/Steam Deck the old behaviour stays; there, please try RX_VK_KEEP_RETIRED=1 and say whether the device lost goes away.

Release https://github.com/NotRexed/Hookshot/releases/tag/fast-updates no longer gives back memory the GPU used, on Windows (it was meant for a Linux AMD driver; fuxau traced the Arc device lost to it in #17, and the AMD logs show device lost right after it). If you had device lost, could you try this release and tell us? On Linux/Steam Deck the old behaviour stays; there, please try `RX_VK_KEEP_RETIRED=1` and say whether the device lost goes away.

aerodevxp commented

2026-11-08 18:58:14 +00:00

(Migrated from github.com)

For me, it loads now on the Z1 Extreme and RX 6800 individually, so this issue is fixed. I've got other issues though, like very very low FPS due to low GPU clocks? Even manually setting the clocks using LACT doesn't update them fast enough for it to have a difference in game. The title screen is fine, this just happens during the first time you can play after the opening cutscene. Should I open a new issue?

nogrannydont commented

2026-11-09 02:35:50 +00:00

(Migrated from github.com)

First cut scene works great, after the zelda splash screen, fades to black and then picture never comes back. you can hear the tree talk screen stays black and then after a few minutes seems to crash. Using an Intel B580 card.
hookshot_log.txt

First cut scene works great, after the zelda splash screen, fades to black and then picture never comes back. you can hear the tree talk screen stays black and then after a few minutes seems to crash. Using an Intel B580 card. [hookshot_log.txt](https://github.com/user-attachments/files/34560959/hookshot_log.txt)

NotRexed commented

2026-11-09 05:46:22 +00:00

(Migrated from github.com)

Tracked in #998, follow there. That issue collects every report of a black screen with audio after the intro, 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.

Tracked in #998, follow there. That issue collects every report of a black screen with audio after the intro, 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`.