MASSIVE FPS drop after updating to v2.0.13 #1733

Closed

opened 2026-11-10 14:53:11 +00:00 by purplesanz · 1 comment

purplesanz commented

2026-11-10 14:53:11 +00:00

(Migrated from github.com)

Hookshot version

v2.0.13

What kind of problem

Low fps or stutter

What happened

Yesterday, I was getting 27 - 30 - even 45 FPS on the first dungeon (Deku Tree), v2.0.11. Today, I updated to v2.0.13 and all I'm getting is 5 FPS no matter what I do.

Where in the game

Inside Deku Tree

How often

Every time

Graphics card and driver version

GTX 1650 Super, NVIDIA 596.49

CPU, RAM and operating system

Ryzen 5 3600, 8 GB, Windows 10

Changes from the defaults

No response

Other software hooked into the game

No, nothing hooked in

hookshot_log.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.0.13 ### What kind of problem Low fps or stutter ### What happened Yesterday, I was getting 27 - 30 - even 45 FPS on the first dungeon (Deku Tree), v2.0.11. Today, I updated to v2.0.13 and all I'm getting is 5 FPS no matter what I do. ### Where in the game Inside Deku Tree ### How often Every time ### Graphics card and driver version GTX 1650 Super, NVIDIA 596.49 ### CPU, RAM and operating system Ryzen 5 3600, 8 GB, Windows 10 ### Changes from the defaults _No response_ ### Other software hooked into the game No, nothing hooked in ### hookshot_log.txt [hookshot_log.txt](https://github.com/user-attachments/files/34635360/hookshot_log.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.

NotRexed commented

2026-11-11 21:23:46 +00:00

(Migrated from github.com)

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