Black screen

freneticlibra958-netizen commented

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

(Migrated from github.com)

on the second game start and onward, loading a save will result in the screen being black, though when touching the controller you can hear link moving around, so the game is working, but the screen isn't. Only starting a new game fixes this.

hookshot_log.txt

on the second game start and onward, loading a save will result in the screen being black, though when touching the controller you can hear link moving around, so the game is working, but the screen isn't. Only starting a new game fixes this. [hookshot_log.txt](https://github.com/user-attachments/files/34522490/hookshot_log.txt)

resnato commented

2026-11-07 15:23:33 +00:00

(Migrated from github.com)

Exact same issue here, pausing works but the screen doesn't change also

<img width="1280" height="755" alt="Image" src="https://github.com/user-attachments/assets/ca0d08a5-be4a-4c83-82b5-15624ce61b26" /> Exact same issue here, pausing works but the screen doesn't change also

GsxRoarK4 commented

2026-11-07 15:24:29 +00:00

(Migrated from github.com)

Same issue after update. It was working. But even if I start a new game it's still black and you can hear sound. This is using Nvidia.

ArcaPhria commented

2026-11-07 15:27:29 +00:00

(Migrated from github.com)

Mismo problema después de la actualización. Estaba funcionando. Pero incluso si comienzo un nuevo juego, sigue siendo negro y puedes escuchar el sonido.

Hey, I have the exact same issue and it turns out it’s an Intel Arc driver compatibility problem.

I opened a dedicated report for this, and one of the main project collaborators replied. He explained that they don't have Intel Arc GPUs on hand to test or debug the code.

He asked if we could share our hookshot_log.txt files so they can get an idea of what's breaking, or if anyone with an Intel Arc card could volunteer as a test subject to try out experimental builds and send back feedback.

If you are on an Intel Arc card, please stop by the issue thread I made so we can centralize this and help them fix it.

> Mismo problema después de la actualización. Estaba funcionando. Pero incluso si comienzo un nuevo juego, sigue siendo negro y puedes escuchar el sonido. Hey, I have the exact same issue and it turns out it’s an Intel Arc driver compatibility problem. I opened a dedicated report for this, and one of the main project collaborators replied. He explained that they don't have Intel Arc GPUs on hand to test or debug the code. He asked if we could share our `hookshot_log.txt` files so they can get an idea of what's breaking, or if anyone with an Intel Arc card could volunteer as a test subject to try out experimental builds and send back feedback. If you are on an Intel Arc card, please stop by the issue thread I made so we can centralize this and help them fix it.

thomasvanschoren-rgb commented

2026-11-07 15:29:22 +00:00

(Migrated from github.com)

same is happening with nvidia

resnato commented

2026-11-07 15:32:00 +00:00

(Migrated from github.com)

Here's my log - 1660s 6gb / Ryzen 7 5800x

hookshot_log.txt

Here's my log - 1660s 6gb / Ryzen 7 5800x [hookshot_log.txt](https://github.com/user-attachments/files/34522644/hookshot_log.txt)

NotRexed commented

2026-11-07 16:05:30 +00:00

(Migrated from github.com)

Thanks for the logs. Both show the game itself running (sound, input) while the 3D scene is never drawn on a second start, and I can't reproduce it here with the same build (100% or Auto resolution, English or Spanish, loading a save on a second start all draw normally). What's different about a second start is the caches the first start writes, so could someone try this:

Close the game, and in the game folder delete (or move away) hookshot_prepared.bin, hookshot_programs.bin and mkw_vk_pipelines.bin.
Start the game and load your save.

Does it work again? (The first start after deleting them is slower: shaders are rebuilt.) Please also paste your hookshot_options.ini and say whether Frame generation is on. That will tell me which cache, or which option, causes it.

Thanks for the logs. Both show the game itself running (sound, input) while the 3D scene is never drawn on a second start, and I can't reproduce it here with the same build (100% or Auto resolution, English or Spanish, loading a save on a second start all draw normally). What's different about a second start is the caches the first start writes, so could someone try this: 1. Close the game, and in the game folder delete (or move away) `hookshot_prepared.bin`, `hookshot_programs.bin` and `mkw_vk_pipelines.bin`. 2. Start the game and load your save. Does it work again? (The first start after deleting them is slower: shaders are rebuilt.) Please also paste your `hookshot_options.ini` and say whether Frame generation is on. That will tell me which cache, or which option, causes it.

freneticlibra958-netizen commented

2026-11-07 16:17:10 +00:00

(Migrated from github.com)

I can confirm that after deleting hookshot_prepared.bin, hookshot_programs.bin and mkw_vk_pipelines.bin the game works again, and subsequent game restarts don't seem to be breaking again.
still, here are both files(config file is a .txt because github woulnt let me post it as a .ini):
hookshot_log.txt

hookshot_options.txt

I can confirm that after deleting `hookshot_prepared.bin`, `hookshot_programs.bin` and `mkw_vk_pipelines.bin` the game works again, and subsequent game restarts don't seem to be breaking again. still, here are both files(config file is a .txt because github woulnt let me post it as a .ini): [hookshot_log.txt](https://github.com/user-attachments/files/34523521/hookshot_log.txt) [hookshot_options.txt](https://github.com/user-attachments/files/34523530/hookshot_options.txt)

sansyundertale commented

2026-11-07 16:43:12 +00:00

(Migrated from github.com)

when I encountered this, I was able to workaround by opening the settings menu and changing the resolution option back and forth. Image gets fixed, then you can go back to whatever resolution setting you were using.

herdayu commented

2026-11-07 18:26:11 +00:00

(Migrated from github.com)

Yeah same as mine. On the second i launched the game it only showed black screen with loading icon and I can only heard the sound and I can move Link but there were nothing on the screen.

NotRexed commented

2026-11-07 19:40:57 +00:00

(Migrated from github.com)

For newer reports here: close the game, delete hookshot_prepared.bin, hookshot_programs.bin and mkw_vk_pipelines.bin in the game folder, and start again; that brought the picture back for the reporter. Changing the resolution in the Insert menu back and forth also restores it. The cause is still being looked into.

For newer reports here: close the game, delete `hookshot_prepared.bin`, `hookshot_programs.bin` and `mkw_vk_pipelines.bin` in the game folder, and start again; that brought the picture back for the reporter. Changing the resolution in the Insert menu back and forth also restores it. The cause is still being looked into.

kai2143 commented

2026-11-08 00:41:16 +00:00

(Migrated from github.com)

I did everything NotRexed said to here and nothing changed, i even completely deleted every file and redid the installation completely with no luck. Ill attatch my options and logs if it can help. ive tried using frame generation both on and off without any difference.

hookshot_log.txt

hookshot_options.txt

I did everything NotRexed said to here and nothing changed, i even completely deleted every file and redid the installation completely with no luck. Ill attatch my options and logs if it can help. ive tried using frame generation both on and off without any difference. [hookshot_log.txt](https://github.com/user-attachments/files/34531409/hookshot_log.txt) [hookshot_options.txt](https://github.com/user-attachments/files/34531587/hookshot_options.txt)

NotRexed commented

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

(Migrated from github.com)

I did everything NotRexed said to here and nothing changed, i even completely deleted every file and redid the installation completely with no luck. Ill attatch my options and logs if it can help. ive tried using frame generation both on and off without any difference.

hookshot_log.txt

hookshot_options.txt

I'm working on a fix, thanks for the logs

> I did everything NotRexed said to here and nothing changed, i even completely deleted every file and redid the installation completely with no luck. Ill attatch my options and logs if it can help. ive tried using frame generation both on and off without any difference. > > [hookshot_log.txt](https://github.com/user-attachments/files/34531409/hookshot_log.txt) > > [hookshot_options.txt](https://github.com/user-attachments/files/34531587/hookshot_options.txt) I'm working on a fix, thanks for the logs

Raulvictord commented

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

(Migrated from github.com)

Another data point, with logs from four runs. RTX 3050 6GB Laptop GPU, NVIDIA driver 621.14, Windows 11, i7-13650HX; source builds; hookshot_options.ini all defaults (Custom preset, Auto resolution, frame generation off); language pt-BR. The save was made in an emulator and copied into user\save\; a new game on the first start drew fine.

Here the black screen after loading a save was the device loss of #150, and current main fixes it.

On build e40306e (foliage-linux-updater + 133 commits), 3 of 3 save loads went the same way:

while the save loads: submit N failed (-4), device lost, the checkpoint marker in dispatch of program 53caac5f38279735 (frames 1084, 3652 and 853; the program named in #339), after write-backs of five pools and the dispatch of 53fcaee4dc45c6ee.
from then on the screen stays black with sound and input working, and the Insert menu does not show.
deleting hookshot_prepared.bin, hookshot_programs.bin and mkw_vk_pipelines.bin made no difference: runs 2 and 3 started with fresh caches (prepared 14179 shader programs (21671 new, 43 failed) in 28.2 s) and lost the device the same way.

On build 4cfa08f (device-lost-fix + 12 commits), fresh caches: the same save loads and draws, about 14 minutes of play at 60 fps, no device lost in the log.

So anyone with this symptom could look for device lost in hookshot_log.txt just before the screen went black. If it is there, the device-lost-fix release (9bb52a9, issue #150) should fix it.

Side note, probably unrelated: in all four runs, including the good one, the log has a draw without a program; its code: 1:4b818bef4b69909a 6:2c56dc1006942f74 around the save load (about 40 frames on the good build; every frame after the device loss on the old one). The picture is fine with it, so it is not the black screen; it may be one of the 43 programs that fail to prepare on this driver.

Logs attached: run 1 (e40306e, black screen) and run 4 (4cfa08f, OK).

[hos Presentation Thread] vk: submit 7590 failed (-4)
[hos Presentation Thread] vk: device lost: reading the checkpoints
[hos Presentation Thread] vk: device lost: 2 checkpoints (39394 markers set)
[hos Presentation Thread] vk:   stage 0x1: marker 39065 (dispatch of program 53caac5f38279735, frame 1084)
[hos Presentation Thread] vk:     before: write-back of pool 000000112e000000
[hos Presentation Thread] vk:     before: write-back of pool 000000112a000000
[hos Presentation Thread] vk:     before: write-back of pool 000000116b000000
[hos Presentation Thread] vk:     before: write-back of pool 000000100d000000
[hos Presentation Thread] vk:     before: write-back of pool 0000001020000000
[hos Presentation Thread] vk:     before: dispatch of program 53fcaee4dc45c6ee
[hos Presentation Thread] vk:     after: marker 39066 dispatch of program 3e6fe279463b020e, frame 1084

hookshot_log_black-screen-after-load_2026-11-08_0008.txt

hookshot_log_run4_new-build-4cfa08f_2026-11-08.txt

Another data point, with logs from four runs. RTX 3050 6GB Laptop GPU, NVIDIA driver 621.14, Windows 11, i7-13650HX; source builds; `hookshot_options.ini` all defaults (Custom preset, Auto resolution, frame generation off); language pt-BR. The save was made in an emulator and copied into `user\save\`; a new game on the first start drew fine. **Here the black screen after loading a save was the device loss of #150, and current main fixes it.** On build e40306e (foliage-linux-updater + 133 commits), 3 of 3 save loads went the same way: - while the save loads: `submit N failed (-4)`, `device lost`, the checkpoint marker in `dispatch of program 53caac5f38279735` (frames 1084, 3652 and 853; the program named in #339), after write-backs of five pools and the dispatch of `53fcaee4dc45c6ee`. - from then on the screen stays black with sound and input working, and the Insert menu does not show. - deleting `hookshot_prepared.bin`, `hookshot_programs.bin` and `mkw_vk_pipelines.bin` made no difference: runs 2 and 3 started with fresh caches (`prepared 14179 shader programs (21671 new, 43 failed) in 28.2 s`) and lost the device the same way. On build 4cfa08f (device-lost-fix + 12 commits), fresh caches: the same save loads and draws, about 14 minutes of play at 60 fps, no `device lost` in the log. So anyone with this symptom could look for `device lost` in `hookshot_log.txt` just before the screen went black. If it is there, the `device-lost-fix` release (9bb52a9, issue #150) should fix it. Side note, probably unrelated: in all four runs, including the good one, the log has `a draw without a program; its code: 1:4b818bef4b69909a 6:2c56dc1006942f74` around the save load (about 40 frames on the good build; every frame after the device loss on the old one). The picture is fine with it, so it is not the black screen; it may be one of the 43 programs that fail to prepare on this driver. Logs attached: run 1 (e40306e, black screen) and run 4 (4cfa08f, OK). ``` [hos Presentation Thread] vk: submit 7590 failed (-4) [hos Presentation Thread] vk: device lost: reading the checkpoints [hos Presentation Thread] vk: device lost: 2 checkpoints (39394 markers set) [hos Presentation Thread] vk: stage 0x1: marker 39065 (dispatch of program 53caac5f38279735, frame 1084) [hos Presentation Thread] vk: before: write-back of pool 000000112e000000 [hos Presentation Thread] vk: before: write-back of pool 000000112a000000 [hos Presentation Thread] vk: before: write-back of pool 000000116b000000 [hos Presentation Thread] vk: before: write-back of pool 000000100d000000 [hos Presentation Thread] vk: before: write-back of pool 0000001020000000 [hos Presentation Thread] vk: before: dispatch of program 53fcaee4dc45c6ee [hos Presentation Thread] vk: after: marker 39066 dispatch of program 3e6fe279463b020e, frame 1084 ``` [hookshot_log_black-screen-after-load_2026-11-08_0008.txt](https://github.com/user-attachments/files/34537175/hookshot_log_black-screen-after-load_2026-11-08_0008.txt) [hookshot_log_run4_new-build-4cfa08f_2026-11-08.txt](https://github.com/user-attachments/files/34537178/hookshot_log_run4_new-build-4cfa08f_2026-11-08.txt)

ivanrannih-cell commented

2026-11-08 07:29:52 +00:00

(Migrated from github.com)

Here is my log

hookshot_log.txt

Here is my log [hookshot_log.txt](https://github.com/user-attachments/files/34539440/hookshot_log.txt)

NotRexed commented

2026-11-08 09:56:27 +00:00

(Migrated from github.com)

Fixed for the known causes (compute shaders now compile in the background; cards without mesh shaders get a clear message). Please update from https://github.com/NotRexed/Hookshot/releases/latest and open a new issue with hookshot_log.txt if it is still black.

github-sync referenced this issue

2026-11-12 06:25:52 +00:00

docs(triage): complete part of Phase 0 of the roadmap #522

Rows
Columns

Black screen #195