very bad fps on 30 series #227

Closed

opened 2026-11-07 16:46:52 +00:00 by bobpimentinha · 4 comments

bobpimentinha commented

2026-11-07 16:46:52 +00:00

(Migrated from github.com)

new build is a little better than before, but it's almost unplayable in my laptop RTX3050 intel i5 12500H

<img width="1587" height="926" alt="Image" src="https://github.com/user-attachments/assets/2043cdc6-bf3f-40b4-a95c-e239ed42e6c4" /> new build is a little better than before, but it's almost unplayable in my laptop RTX3050 intel i5 12500H

RatCatcherVr-dev commented

2026-11-07 17:05:48 +00:00

(Migrated from github.com)

mine runs like 25-35 fps and thats just walking in the main area

mine runs like 25-35 fps and thats just walking in the main area <img width="1919" height="1079" alt="Image" src="https://github.com/user-attachments/assets/4ec38a40-5bd4-43f4-a813-a4c491edbf6a" />

NotRexed commented

2026-11-07 19:40:44 +00:00

(Migrated from github.com)

Could you attach hookshot_log.txt (in the game folder, next to hookshot.exe) from https://github.com/NotRexed/Hookshot/releases/tag/foliage-linux-updater? On laptops the log shows whether the game runs on the RTX or on the Intel graphics, and how much VRAM it uses; Resolution 50% in the Insert menu also helps on 4 GB cards.

Could you attach `hookshot_log.txt` (in the game folder, next to `hookshot.exe`) from https://github.com/NotRexed/Hookshot/releases/tag/foliage-linux-updater? On laptops the log shows whether the game runs on the RTX or on the Intel graphics, and how much VRAM it uses; Resolution 50% in the Insert menu also helps on 4 GB cards.

metroid98 commented

2026-11-08 07:43:24 +00:00

(Migrated from github.com)

Numbers from a Linux RTX 3060 12 GB, in case they help with the 30 series reports. AI-assisted: the run was scripted and the numbers collected by Claude Code on my behalf.

Machine: Bazzite 45 (Fedora, KDE Wayland), NVIDIA 615.78, Ryzen CPU with 12 threads, 15 GB RAM. Build fa22c2d (release compile-retry, built from my own dump with the AppImage). Headless run (HOS_HEADLESS=1, renders offscreen at 1920x1080, scripted input via HOS_INPUT_LIVE), so no window or compositor cost. I did not set Resolution to 50%.

Title screen (after the 57 s first-start shader prepare, 21714 programs, 0 failed): median 56 fps (40-60), GPU time 6.5 ms/frame, VRAM 2036 MB used, 25 pipelines.

New Game to Kokiri Forest (intro, Deku Tree cutscene, then walking in the village and talking to Saria, first visit, about 10 min of play):

Cutscenes: median 30 fps (5 s windows, max 37, not counting the load stall below), GPU time ~17 ms/frame.
Walking around the village: median 27 fps (min 17, max 37). Present intervals over about 6600 frames: 74% are 30-40 ms, 9% are 22-30 ms, 1% are under 22 ms and 15% (1023 of 6626) are over 40 ms. It never reached 50 or 60 fps here.
Per frame while walking: ~930 draws, ~125 dispatches, ~145 passes, 6 submits. GPU time 15-18 ms, replay CPU "submit" about 13 ms, so the card is not saturated; GPU-bound wait stayed at 0.0 ms.
Stalls on first visit: pipelines are compiled on demand, 1277 pipelines (218 s of compile time in total, 400 programs, 0 failed) by the end of the run. The log has slow submit lines of 18.9 s, 14.0 s, 9.1 s, 7.9 s and 4.4 s, and a 47 s window at 1.6 fps while entering the forest (the frame counter advanced 77 frames). Most of the time is in draw or dispatch, i.e. waiting for a pipeline. I have not yet gone back through the same areas a second time, so I can't say yet how much of the 27 fps is first-visit compile and how much is steady state.
VRAM and RAM: VRAM rose from 2 GB at the title to 10.8 GB used of 11.4 GB allowed in the village (textures 5.5 GB of a 6.1 GB budget, 2572 textures, ~1.9 GB free inside the blocks). nvidia-smi shows 11.3 GB used. Process RSS was 11.5 GB of the 15 GB RAM (working set 11.2 GB).
does not lower lines: 0. Failed programs: 0. Vulkan validation was not enabled.

Can run the same route again with a second pass, other settings (Resolution 50%, RX_VK_MMA_SOFTWARE) or a profile if that would help; happy to test any of the open perf PRs on this card too.

Numbers from a Linux RTX 3060 12 GB, in case they help with the 30 series reports. AI-assisted: the run was scripted and the numbers collected by Claude Code on my behalf. **Machine:** Bazzite 45 (Fedora, KDE Wayland), NVIDIA 615.78, Ryzen CPU with 12 threads, 15 GB RAM. Build `fa22c2d` (release `compile-retry`, built from my own dump with the AppImage). Headless run (`HOS_HEADLESS=1`, renders offscreen at 1920x1080, scripted input via `HOS_INPUT_LIVE`), so no window or compositor cost. I did not set Resolution to 50%. **Title screen** (after the 57 s first-start shader prepare, 21714 programs, 0 failed): median 56 fps (40-60), GPU time 6.5 ms/frame, VRAM 2036 MB used, 25 pipelines. **New Game to Kokiri Forest** (intro, Deku Tree cutscene, then walking in the village and talking to Saria, first visit, about 10 min of play): - Cutscenes: median 30 fps (5 s windows, max 37, not counting the load stall below), GPU time ~17 ms/frame. - Walking around the village: median **27 fps** (min 17, max 37). Present intervals over about 6600 frames: 74% are 30-40 ms, 9% are 22-30 ms, 1% are under 22 ms and 15% (1023 of 6626) are over 40 ms. It never reached 50 or 60 fps here. - Per frame while walking: ~930 draws, ~125 dispatches, ~145 passes, 6 submits. GPU time 15-18 ms, replay CPU "submit" about 13 ms, so the card is not saturated; GPU-bound wait stayed at 0.0 ms. - **Stalls on first visit:** pipelines are compiled on demand, 1277 pipelines (218 s of compile time in total, 400 programs, 0 failed) by the end of the run. The log has `slow submit` lines of 18.9 s, 14.0 s, 9.1 s, 7.9 s and 4.4 s, and a 47 s window at 1.6 fps while entering the forest (the frame counter advanced 77 frames). Most of the time is in `draw` or `dispatch`, i.e. waiting for a pipeline. I have not yet gone back through the same areas a second time, so I can't say yet how much of the 27 fps is first-visit compile and how much is steady state. - **VRAM and RAM:** VRAM rose from 2 GB at the title to **10.8 GB used of 11.4 GB allowed** in the village (textures 5.5 GB of a 6.1 GB budget, 2572 textures, ~1.9 GB free inside the blocks). `nvidia-smi` shows 11.3 GB used. Process RSS was 11.5 GB of the 15 GB RAM (working set 11.2 GB). - `does not lower` lines: **0**. Failed programs: 0. Vulkan validation was not enabled. Can run the same route again with a second pass, other settings (Resolution 50%, `RX_VK_MMA_SOFTWARE`) or a profile if that would help; happy to test any of the open perf PRs on this card too.

NotRexed commented

2026-11-09 05:45:43 +00:00

(Migrated from github.com)

Tracked in #995, follow there. That issue collects every report of low FPS while the GPU is not fully used, and shader stutter, and this one is linked from it with its GPU, version and log details. 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.