MagicBeanDev/Hookshot

Archived

Watch

Fork 0

[Critical Performance Bug] Extreme Resource Usage, 1 FPS, GPU Driver Failure and System Shutdown – AMD RX 5700 XT #1380

Closed

opened 2026-11-09 23:50:11 +00:00 by pedrololix-svg · 2 comments

pedrololix-svg commented

2026-11-09 23:50:11 +00:00

(Migrated from github.com)

Hookshot version

v2.0.11

What kind of problem

Performance / Stability (extremely low FPS, excessive resource usage, freezes, black screen, GPU driver failure, and system shutdown).

What happened

Hello developer,

I'm experiencing a severe performance issue with Hookshot on my system with an AMD Radeon RX 5700 XT.

The issue first appeared in version 2.0.6 and has continued in subsequent releases, including versions 2.0.9, 2.0.10, and 2.0.11.

Since these updates, the game has started consuming an excessive amount of system resources, to the point where the entire computer becomes unresponsive and eventually shuts down.

When launching the game, the audio works very well and sounds completely normal. However, the visual performance is extremely poor:

The game runs at approximately 1 FPS.

The game loads extremely slowly.

The screen gradually becomes completely black.

The computer eventually freezes and shuts down entirely.

The AMD graphics drivers also appear to be removed or become unavailable after the crash, requiring driver recovery or reinstallation.

This makes the game practically impossible to play and, in some cases, affects the stability of the entire system and GPU driver installation.

Version history:

Version 2.0.0 and earlier: The game ran smoothly on my AMD GPU.

Version 2.0.6: The performance issues first appeared.

Versions 2.0.9, 2.0.10 and 2.0.11: The problems persisted, with extreme resource consumption, approximately 1 FPS, extremely slow loading, black screens, GPU driver failures and eventual system shutdown.

System information:

GPU: AMD Radeon RX 5700 XT

GPU architecture: RDNA 1

Operating system: Windows

GPU driver: AMD Radeon

Questions / Suggestions:

Could these newer versions have introduced a memory leak or excessive GPU/CPU resource consumption?

Is there a possible regression in the rendering pipeline or shader compilation affecting AMD GPUs?

Could the game be entering an infinite rendering or shader compilation loop?

Could the game be causing GPU driver crashes or system-level instability?

Could you investigate the performance differences between version 2.0.0 and versions 2.0.6 and later?

The most concerning part is that the game not only becomes unplayable but can also cause the entire computer to freeze and shut down. The AMD graphics drivers are also affected after these incidents.

The audio continues working normally while the visual rendering is almost completely stalled, which makes me suspect a problem related to graphics rendering or GPU resource management.

I hope this issue can be investigated, as the game was running smoothly on my hardware in earlier versions.

Thank you for your work on the project!

Where in the game

anywhere

How often

Every time

Graphics card and driver version

AMD RX 5700 XT

CPU, RAM and operating system

xeon e5 2680 v4, 16gb, win 11

Changes from the defaults

No response

Other software hooked into the game

No, nothing hooked in

hookshot_log.txt

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

Screenshots or video

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.0.11 ### What kind of problem Performance / Stability (extremely low FPS, excessive resource usage, freezes, black screen, GPU driver failure, and system shutdown). ### What happened Hello developer, I'm experiencing a severe performance issue with Hookshot on my system with an AMD Radeon RX 5700 XT. The issue first appeared in version 2.0.6 and has continued in subsequent releases, including versions 2.0.9, 2.0.10, and 2.0.11. Since these updates, the game has started consuming an excessive amount of system resources, to the point where the entire computer becomes unresponsive and eventually shuts down. When launching the game, the audio works very well and sounds completely normal. However, the visual performance is extremely poor: The game runs at approximately 1 FPS. The game loads extremely slowly. The screen gradually becomes completely black. The computer eventually freezes and shuts down entirely. The AMD graphics drivers also appear to be removed or become unavailable after the crash, requiring driver recovery or reinstallation. This makes the game practically impossible to play and, in some cases, affects the stability of the entire system and GPU driver installation. Version history: Version 2.0.0 and earlier: The game ran smoothly on my AMD GPU. Version 2.0.6: The performance issues first appeared. Versions 2.0.9, 2.0.10 and 2.0.11: The problems persisted, with extreme resource consumption, approximately 1 FPS, extremely slow loading, black screens, GPU driver failures and eventual system shutdown. System information: GPU: AMD Radeon RX 5700 XT GPU architecture: RDNA 1 Operating system: Windows GPU driver: AMD Radeon Questions / Suggestions: Could these newer versions have introduced a memory leak or excessive GPU/CPU resource consumption? Is there a possible regression in the rendering pipeline or shader compilation affecting AMD GPUs? Could the game be entering an infinite rendering or shader compilation loop? Could the game be causing GPU driver crashes or system-level instability? Could you investigate the performance differences between version 2.0.0 and versions 2.0.6 and later? The most concerning part is that the game not only becomes unplayable but can also cause the entire computer to freeze and shut down. The AMD graphics drivers are also affected after these incidents. The audio continues working normally while the visual rendering is almost completely stalled, which makes me suspect a problem related to graphics rendering or GPU resource management. I hope this issue can be investigated, as the game was running smoothly on my hardware in earlier versions. Thank you for your work on the project! ### Where in the game anywhere ### How often Every time ### Graphics card and driver version AMD RX 5700 XT ### CPU, RAM and operating system xeon e5 2680 v4, 16gb, win 11 ### Changes from the defaults _No response_ ### Other software hooked into the game No, nothing hooked in ### hookshot_log.txt [hookshot_log.1.txt](https://github.com/user-attachments/files/34604657/hookshot_log.1.txt) [hookshot_log.2.txt](https://github.com/user-attachments/files/34604658/hookshot_log.2.txt) [hookshot_log.3.txt](https://github.com/user-attachments/files/34604661/hookshot_log.3.txt) [hookshot_log.4.txt](https://github.com/user-attachments/files/34604659/hookshot_log.4.txt) [hookshot_log.txt](https://github.com/user-attachments/files/34604660/hookshot_log.txt) ### Screenshots or video <img width="1308" height="789" alt="Image" src="https://github.com/user-attachments/assets/22aa6ae6-4d00-4f73-aebf-12abadb29258" /> ### 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.

juanreyesrendon commented

2026-11-09 23:51:09 +00:00

(Migrated from github.com)

I have the same issue, is like the game doesn´t use the graphic card.

<img width="965" height="723" alt="Image" src="https://github.com/user-attachments/assets/7ad48038-4a24-4d59-b4db-dbf2d696811c" /> I have the same issue, is like the game doesn´t use the graphic card.

😕 1

NotRexed commented

2026-11-10 00:16:56 +00:00

(Migrated from github.com)

Thanks for the report. The RX 5700 XT has no mesh shaders, and 1 fps with resource use growing until the PC stops, since v2.0.6, is tracked in #1001 (memory growth also in #1072). Fixes for the fallback (#1314, #1317) are planned for the next release. Closing this as a duplicate; please follow #1001.

Commenting is not possible because the repository is archived.