Graphics card was reset after the first game cutscene #2139

Closed

opened 2026-11-11 04:42:10 +00:00 by Move36m · 3 comments

Move36m commented

2026-11-11 04:42:10 +00:00

(Migrated from github.com)

Hookshot version

v2.1.0

What kind of problem

Crash, freeze or black screen

What happened

The game launches, I configure it as usual, and I watch the first cutscene; then, the screens on both of my monitors go black for a few seconds, and the game closes.

Linux Cachy OS KDE plasma 32gb ram

Where in the game

after first cutscene

How often

Every time

Graphics card and driver version

Graphics card AMD Radeon RX 6750XT

CPU, RAM and operating system

Ryzen 7 5700x

Changes from the defaults

full hd, native, balanced 8gb. no fsr.

Other software hooked into the game

No, nothing hooked in

hookshot_log.txt

hookshot_log.1.txt

hookshot_log.2.txt

Screenshots or video

No response

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 Crash, freeze or black screen ### What happened The game launches, I configure it as usual, and I watch the first cutscene; then, the screens on both of my monitors go black for a few seconds, and the game closes. Linux Cachy OS KDE plasma 32gb ram ### Where in the game after first cutscene ### How often Every time ### Graphics card and driver version Graphics card AMD Radeon RX 6750XT ### CPU, RAM and operating system Ryzen 7 5700x ### Changes from the defaults full hd, native, balanced 8gb. no fsr. ### Other software hooked into the game No, nothing hooked in ### hookshot_log.txt [hookshot_log.txt](https://github.com/user-attachments/files/34670486/hookshot_log.txt) [hookshot_log.1.txt](https://github.com/user-attachments/files/34670489/hookshot_log.1.txt) [hookshot_log.2.txt](https://github.com/user-attachments/files/34670492/hookshot_log.2.txt) ### Screenshots or video _No response_ ### 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.

❤️ 2

sageelliott1509-del commented

2026-11-11 09:57:58 +00:00

(Migrated from github.com)

im also having this issue with a 9600x 32gb of ram and a 6800xt using the balanced preset on debian

hookshot_log.1.txt
hookshot_log.2.txt
hookshot_log.3.txt
hookshot_log.4.txt
hookshot_log.txt

im also having this issue with a 9600x 32gb of ram and a 6800xt using the balanced preset on debian [hookshot_log.1.txt](https://github.com/user-attachments/files/34681757/hookshot_log.1.txt) [hookshot_log.2.txt](https://github.com/user-attachments/files/34681758/hookshot_log.2.txt) [hookshot_log.3.txt](https://github.com/user-attachments/files/34681759/hookshot_log.3.txt) [hookshot_log.4.txt](https://github.com/user-attachments/files/34681754/hookshot_log.4.txt) [hookshot_log.txt](https://github.com/user-attachments/files/34681786/hookshot_log.txt)

BlasterA01 commented

2026-11-11 10:58:08 +00:00

(Migrated from github.com)

hookshot_log.txt

AMD Ryzen 9 7940HS w/ Radeon 780M Graphics (4.00 GHz), 16G RAM, 512M VRAM
Windows 11
Hookshot v2.1.0
Thanks for the work that's incredible !

I have a similar issue when I load a save. It losts the GPU then crashes. But first cutscene, no problem, the deku scene ran pretty smooth. Gameplay with FPS drops and parts of texture that become black. Hope this will help ! [hookshot_log.txt](https://github.com/user-attachments/files/34684181/hookshot_log.txt) AMD Ryzen 9 7940HS w/ Radeon 780M Graphics (4.00 GHz), 16G RAM, 512M VRAM Windows 11 Hookshot v2.1.0 Thanks for the work that's incredible !

NotRexed commented

2026-11-11 21:25:26 +00:00

(Migrated from github.com)

Thanks for the report. Reports of the same problem are now collected in #996, which lists this one with your details and links back here, so one fix closes them together and the open list stays readable. Follow #996 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.