MagicBeanDev/Hookshot

Archived

Watch

Fork 0

Low fps (20-25) in Kokiri Forest on GTX 1660 SUPER, GPU only at 60-73% #732

Closed

opened 2026-11-08 19:01:57 +00:00 by Typeexos · 6 comments

Typeexos commented

2026-11-08 19:01:57 +00:00

(Migrated from github.com)

Hookshot version

2.0.0

What kind of problem

Low fps or stutter

What happened

Hi! Thanks a lot for Hookshot, the project is moving really fast. I'd like to report performance on a mid-range setup, in case it helps you optimize for smaller configs.

Setup: GTX 1660 SUPER (6 GB), Ryzen 5 3600, 16 GB RAM, Windows, Hookshot v2.0.0.

What I see: the game runs at 60 fps in light scenes, but only around 20-25 fps in heavy ones like the Kokiri Forest (about 2300 draws per frame in my log). GPU usage stays around 60-73% and no CPU core is maxed out.

What I already tried: resolution at 50% (no real change), shader and pipeline caches fully built (the pipeline count stays stable, so it's not shader compilation), frame generation and the quality presets.

From my log, in a heavy scene: GPU time is about 31.5 ms per frame and the replay submit takes about 21.5 ms on the CPU.

I've attached my hookshot_log.txt from a session where it runs slowly. I'm happy to test any build or option that could help older NVIDIA cards. Thanks again for your work!

Where in the game

kokiri forest

How often

Every time

Graphics card and driver version

gtx 1660 s (6gb)

CPU, RAM and operating system

Ryzen 5 3600 16gbddr4 windows11

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 2.0.0 ### What kind of problem Low fps or stutter ### What happened Hi! Thanks a lot for Hookshot, the project is moving really fast. I'd like to report performance on a mid-range setup, in case it helps you optimize for smaller configs. Setup: GTX 1660 SUPER (6 GB), Ryzen 5 3600, 16 GB RAM, Windows, Hookshot v2.0.0. What I see: the game runs at 60 fps in light scenes, but only around 20-25 fps in heavy ones like the Kokiri Forest (about 2300 draws per frame in my log). GPU usage stays around 60-73% and no CPU core is maxed out. What I already tried: resolution at 50% (no real change), shader and pipeline caches fully built (the pipeline count stays stable, so it's not shader compilation), frame generation and the quality presets. From my log, in a heavy scene: GPU time is about 31.5 ms per frame and the replay submit takes about 21.5 ms on the CPU. I've attached my hookshot_log.txt from a session where it runs slowly. I'm happy to test any build or option that could help older NVIDIA cards. Thanks again for your work! ### Where in the game kokiri forest ### How often Every time ### Graphics card and driver version gtx 1660 s (6gb) ### CPU, RAM and operating system Ryzen 5 3600 16gbddr4 windows11 ### 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/34551671/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.

doomAWL2 commented

2026-11-08 19:05:57 +00:00

(Migrated from github.com)

I'm pretty sure this is RAM related. For me everything was under 100% usage except for RAM. I also have 16 gb of RAM.

Typeexos commented

2026-11-08 19:13:14 +00:00

(Migrated from github.com)

I'm pretty sure this is RAM related. For me everything was under 100% usage except for RAM. I also have 16 gb of RAM.

I tested with everything else closed and the fps stay the same, so I don’t think RAM is the main cause on my side. My GPU and CPU are both under 100% too, and the fps drop depends on the scene (60 fps in light scenes, 20-25 in the Kokiri Forest). I’ll attach my log in case it helps.

> I'm pretty sure this is RAM related. For me everything was under 100% usage except for RAM. I also have 16 gb of RAM. I tested with everything else closed and the fps stay the same, so I don’t think RAM is the main cause on my side. My GPU and CPU are both under 100% too, and the fps drop depends on the scene (60 fps in light scenes, 20-25 in the Kokiri Forest). I’ll attach my log in case it helps.

doomAWL2 commented

2026-11-08 19:26:02 +00:00

(Migrated from github.com)

I'm pretty sure this is RAM related. For me everything was under 100% usage except for RAM. I also have 16 gb of RAM.

I tested with everything else closed and the fps stay the same, so I don’t think RAM is the main cause on my side. My GPU and CPU are both under 100% too, and the fps drop depends on the scene (60 fps in light scenes, 20-25 in the Kokiri Forest). I’ll attach my log in case it helps.

It's definitely your RAM too, your log shows the game pulling nearly 9.8 GB of system memory and over 7 to 8 GB of VRAM working set, which is bottlenecking you alongside those draw calls.

> > I'm pretty sure this is RAM related. For me everything was under 100% usage except for RAM. I also have 16 gb of RAM. > > I tested with everything else closed and the fps stay the same, so I don’t think RAM is the main cause on my side. My GPU and CPU are both under 100% too, and the fps drop depends on the scene (60 fps in light scenes, 20-25 in the Kokiri Forest). I’ll attach my log in case it helps. It's definitely your RAM too, your log shows the game pulling nearly 9.8 GB of system memory and over 7 to 8 GB of VRAM working set, which is bottlenecking you alongside those draw calls.

Typeexos commented

2026-11-08 19:42:10 +00:00

(Migrated from github.com)

I'm pretty sure this is RAM related. For me everything was under 100% usage except for RAM. I also have 16 gb of RAM.

I tested with everything else closed and the fps stay the same, so I don’t think RAM is the main cause on my side. My GPU and CPU are both under 100% too, and the fps drop depends on the scene (60 fps in light scenes, 20-25 in the Kokiri Forest). I’ll attach my log in case it helps.

It's definitely your RAM too, your log shows the game pulling nearly 9.8 GB of system memory and over 7 to 8 GB of VRAM working set, which is bottlenecking you alongside those draw calls.

It would be cool if the developer could release an update that reduces VRAM and RAM usage for lower-end machines.

> > > I'm pretty sure this is RAM related. For me everything was under 100% usage except for RAM. I also have 16 gb of RAM. > > > > > > I tested with everything else closed and the fps stay the same, so I don’t think RAM is the main cause on my side. My GPU and CPU are both under 100% too, and the fps drop depends on the scene (60 fps in light scenes, 20-25 in the Kokiri Forest). I’ll attach my log in case it helps. > > It's definitely your RAM too, your log shows the game pulling nearly 9.8 GB of system memory and over 7 to 8 GB of VRAM working set, which is bottlenecking you alongside those draw calls. It would be cool if the developer could release an update that reduces VRAM and RAM usage for lower-end machines.

Typeexos commented

2026-11-09 01:36:25 +00:00

(Migrated from github.com)

Update with v2.0.4 on the GTX 1660 SUPER (6 GB), Ryzen 5 3600, 16 GB RAM:

I made it through the whole Deku Tree at around 45-50 fps, but Hyrule Field drops to about 10 fps.

In my log, the Deku Tree stays under the VRAM budget (about 4.8-5.0 GB used of ~5.2 GB allowed) with fewer draws per frame. In Hyrule Field, VRAM goes above the budget (5.3-5.5 GB used) and draws go up to 2000+ per frame. At similar draw counts, GPU time per frame is about 1.5x higher when VRAM is over budget (700-1100 draws: ~45 fps / 16.7 ms under budget vs ~29 fps / 26.4 ms over budget).

Task Manager while playing shows Dedicated GPU memory at 5.6/6.0 GB. Lowering the resolution to 50% did not change much, so it looks more like VRAM and scene load than pixel count.

I've attached my latest hookshot_log.txt from a session in Hyrule Field. Happy to test any build or option that could reduce VRAM use on 6 GB cards.

hookshot_log.txt

Update with v2.0.4 on the GTX 1660 SUPER (6 GB), Ryzen 5 3600, 16 GB RAM: I made it through the whole Deku Tree at around 45-50 fps, but Hyrule Field drops to about 10 fps. In my log, the Deku Tree stays under the VRAM budget (about 4.8-5.0 GB used of ~5.2 GB allowed) with fewer draws per frame. In Hyrule Field, VRAM goes above the budget (5.3-5.5 GB used) and draws go up to 2000+ per frame. At similar draw counts, GPU time per frame is about 1.5x higher when VRAM is over budget (700-1100 draws: ~45 fps / 16.7 ms under budget vs ~29 fps / 26.4 ms over budget). Task Manager while playing shows Dedicated GPU memory at 5.6/6.0 GB. Lowering the resolution to 50% did not change much, so it looks more like VRAM and scene load than pixel count. I've attached my latest hookshot_log.txt from a session in Hyrule Field. Happy to test any build or option that could reduce VRAM use on 6 GB cards. [hookshot_log.txt](https://github.com/user-attachments/files/34559613/hookshot_log.txt)

NotRexed commented

2026-11-09 05:54:49 +00:00

(Migrated from github.com)

Tracked in #993, follow there. That issue collects every report of garbled or rainbow textures that get worse over play time, and this one is linked from it with its GPU, version and log details. It is a known issue in v2.0.6 and not fixed yet. 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.

Commenting is not possible because the repository is archived.