Low FPS/stutter #1056

Closed

opened 2026-11-09 08:30:03 +00:00 by kiv9393 · 2 comments

kiv9393 commented

2026-11-09 08:30:03 +00:00

(Migrated from github.com)

Hookshot version

v2.0.6

What kind of problem

Graphics (missing, black or wrong-coloured things, lighting, flicker)

What happened

On a 6 GB laptop GPU (RTX 4050 Laptop, Linux Mint) the game started and played the intro video at about 55 fps. With the default settings it then fell to about 0.1 to 3 fps while loading Kokiri Forest and in the Deku Tree cutscene, and the picture looked wrong. It did not crash.

Numbers from hookshot_log.txt of that slow run:

"slow submit: 13696.6 ms", a "queue submit 7577.3" stall, and "0.1 fps over the last 9.9 s".
Later at about 1.8 fps: "GPU time 212.1 ms a frame (the longest submission 2143.3 ms)", 400 draws a frame, GPU use 100%, graphics memory 3392 of 5640 MB.
Many "in play: graphics/mesh ..." and "NVN2 program ... lowered with extended registers" lines taking seconds each on the first visit.
Repeated "storage buffer NOT bound (reads zeros): program da7a7ab28b8e73d9 stage 1 c5+0 addr 0x4180000000000200 size 0x20" while the picture looked wrong.
16 lines "view of texture 0x1133ccb000 (vk 139) as vk 95 type 1 ... not made" when the forest started loading.

After I changed settings in the menu (listed below), the same place ran at about 26 fps (GPU 57%, CPU 562%) and later 58 to 60 fps (the counter showed "58 FPS, game 28"). The picture in my later Kokiri Forest screenshot looks normal. In the last 34 seconds of one long log: GPU time 3.5 ms a frame, 0 waits for shaders, graphics memory 4.6 to 5.0 GB of 5.47 GB allowed. The GPU was not throttled: 18 to 28 W, 51 to 53 C, plugged in, clock 1800 to 2610 of 3105 MHz.

Notes:

My very first start was interrupted. I closed the window about 30 seconds into "preparing shaders", so shader preparation may have been incomplete, which may explain part of the stalls. I did not repeat the test with a clean first start.
I changed several settings at once, so I do not know which one fixed it.
I built with v2.0.6 (AppImage plus the missing header added by hand). v2.0.7 only fixes that packaging bug, so the game code should be the same.
On Linux the launcher's Play button sends the game's output nowhere, so the first start (shader preparation, more than 12 minutes at about 150% CPU for me) showed no progress and looked frozen. A progress message in the launcher would help Linux users.
Suggestion: on a 6 GB card the default settings may be too heavy. Suggesting or auto-selecting "Low (6GB)" might spare other 6 GB owners the 2 fps start.

Where in the game

Kokiri Forest while loading, then the Deku Tree cutscene (start of a new game)

How often

Once so far

Graphics card and driver version

NVIDIA GeForce RTX 4050 Laptop GPU (6 GB), NVIDIA driver 580.126.09 (Vulkan on the NVIDIA card via PRIME offload; the laptop also has an Intel Iris Xe without mesh shader support)

CPU, RAM and operating system

Intel Core i5-12500H, 16 GB RAM, Linux Mint 22.2 Xfce (HP Victus 15-fa1xxx)

Changes from the defaults

Menu settings changed: Quality preset Low (6GB), Resolution 50%, Handheld profile On, Output resolution 2048x1152, Fullscreen On, FPS counter On, Text speed Instant.
Start environment: __NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus=NVIDIA_only __GLX_VENDOR_LIBRARY_NAME=nvidia HOOKSHOT_NO_UPDATE_CHECK=1

Other software hooked into the game

No, nothing hooked in

hookshot_log.txt

hookshot_play_output_run_2.zip

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.6 ### What kind of problem Graphics (missing, black or wrong-coloured things, lighting, flicker) ### What happened On a 6 GB laptop GPU (RTX 4050 Laptop, Linux Mint) the game started and played the intro video at about 55 fps. With the default settings it then fell to about 0.1 to 3 fps while loading Kokiri Forest and in the Deku Tree cutscene, and the picture looked wrong. It did not crash. Numbers from hookshot_log.txt of that slow run: - "slow submit: 13696.6 ms", a "queue submit 7577.3" stall, and "0.1 fps over the last 9.9 s". - Later at about 1.8 fps: "GPU time 212.1 ms a frame (the longest submission 2143.3 ms)", 400 draws a frame, GPU use 100%, graphics memory 3392 of 5640 MB. - Many "in play: graphics/mesh ..." and "NVN2 program ... lowered with extended registers" lines taking seconds each on the first visit. - Repeated "storage buffer NOT bound (reads zeros): program da7a7ab28b8e73d9 stage 1 c5+0 addr 0x4180000000000200 size 0x20" while the picture looked wrong. - 16 lines "view of texture 0x1133ccb000 (vk 139) as vk 95 type 1 ... not made" when the forest started loading. After I changed settings in the menu (listed below), the same place ran at about 26 fps (GPU 57%, CPU 562%) and later 58 to 60 fps (the counter showed "58 FPS, game 28"). The picture in my later Kokiri Forest screenshot looks normal. In the last 34 seconds of one long log: GPU time 3.5 ms a frame, 0 waits for shaders, graphics memory 4.6 to 5.0 GB of 5.47 GB allowed. The GPU was not throttled: 18 to 28 W, 51 to 53 C, plugged in, clock 1800 to 2610 of 3105 MHz. Notes: 1. My very first start was interrupted. I closed the window about 30 seconds into "preparing shaders", so shader preparation may have been incomplete, which may explain part of the stalls. I did not repeat the test with a clean first start. 2. I changed several settings at once, so I do not know which one fixed it. 3. I built with v2.0.6 (AppImage plus the missing header added by hand). v2.0.7 only fixes that packaging bug, so the game code should be the same. 4. On Linux the launcher's Play button sends the game's output nowhere, so the first start (shader preparation, more than 12 minutes at about 150% CPU for me) showed no progress and looked frozen. A progress message in the launcher would help Linux users. 5. Suggestion: on a 6 GB card the default settings may be too heavy. Suggesting or auto-selecting "Low (6GB)" might spare other 6 GB owners the 2 fps start. ### Where in the game Kokiri Forest while loading, then the Deku Tree cutscene (start of a new game) ### How often Once so far ### Graphics card and driver version NVIDIA GeForce RTX 4050 Laptop GPU (6 GB), NVIDIA driver 580.126.09 (Vulkan on the NVIDIA card via PRIME offload; the laptop also has an Intel Iris Xe without mesh shader support) ### CPU, RAM and operating system Intel Core i5-12500H, 16 GB RAM, Linux Mint 22.2 Xfce (HP Victus 15-fa1xxx) ### Changes from the defaults Menu settings changed: Quality preset Low (6GB), Resolution 50%, Handheld profile On, Output resolution 2048x1152, Fullscreen On, FPS counter On, Text speed Instant. Start environment: __NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus=NVIDIA_only __GLX_VENDOR_LIBRARY_NAME=nvidia HOOKSHOT_NO_UPDATE_CHECK=1 ### Other software hooked into the game No, nothing hooked in ### hookshot_log.txt [hookshot_play_output_run_2.zip](https://github.com/user-attachments/files/34570133/hookshot_play_output_run_2.zip) ### 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-09 09:19:00 +00:00

(Migrated from github.com)

Thanks for the thorough notes. Linking to the FPS/stutter tracker #995. Two things in v2.0.8 (out shortly) target what you saw: pipelines are built before the game on install (#939), and 6-8 GB cards keep large textures compressed (#963). The launcher progress on Linux is a fair request.

NotRexed commented

2026-11-09 22:50:35 +00:00

(Migrated from github.com)

Thanks for the report. To keep each problem in one place, this is tracked in #995 (low FPS and stutter), which links your details. Closing this as a duplicate; please follow #995 for updates.

Commenting is not possible because the repository is archived.