Kokiri Forrest unusual GPU fence time in certain camera angle #1120

Open
opened 2026-11-16 12:00:40 +00:00 by Alimjan · 3 comments

Longshot version

v3.0.0-rc4 dev

Channel

Built from source

What kind of problem

Low fps or stutter

What happened

When looking at the opposite angle from the Deku Tree entrance, GPU fence time spikes significantly and the frame rate drops sharply.

Kokiri Forest performance has come a long way since the start — it used to run at only 15–20 fps, and now it can hold a consistent 50 fps most of the time. To reach the final goal of a consistent 50 fps experience, which should be smooth enough with frame generation, I think this issue should be resolved.

Where in the game

Kokiri Forest

How often

Every time

Graphics card and driver version

RTX 5060 Ti, 621.24

CPU, RAM and operating system

Ryzan ThreadRipper 1950x, 64GB and Windows 11

Changes from the defaults

RX_VK_ASYNC=1
RX_VK_FIFO=1

longshot_log.txt

longshot_log

Screenshots or video

Before you send it

  • The problem is still there on the newest release or nightly.
  • I searched the open issues for it.
  • I'm not attaching game files, keys, the game's executable, its .bin caches or saves.
### Longshot version v3.0.0-rc4 dev ### Channel Built from source ### What kind of problem Low fps or stutter ### What happened When looking at the opposite angle from the Deku Tree entrance, GPU fence time spikes significantly and the frame rate drops sharply. Kokiri Forest performance has come a long way since the start — it used to run at only 15–20 fps, and now it can hold a consistent 50 fps most of the time. To reach the final goal of a consistent 50 fps experience, which should be smooth enough with frame generation, I think this issue should be resolved. ### Where in the game Kokiri Forest ### How often Every time ### Graphics card and driver version RTX 5060 Ti, 621.24 ### CPU, RAM and operating system Ryzan ThreadRipper 1950x, 64GB and Windows 11 ### Changes from the defaults RX_VK_ASYNC=1 RX_VK_FIFO=1 ### longshot_log.txt [longshot_log](/attachments/6c145112-6e9f-4669-9050-283dbc23f776) ### Screenshots or video <video src="/attachments/8038ae2a-098c-44a1-bb6f-0a82861040ab" title="longshot_BFpwAJPm5L" controls></video> ### Before you send it - [x] The problem is still there on the newest release or nightly. - [x] I searched the open issues for it. - [x] I'm not attaching game files, keys, the game's executable, its .bin caches or saves.
Collaborator

Possibly related, for context:

  • #410 [Performance] Severe CPU-side rendering bottleneck in Kokiri Forest (21–42 FPS, low GPU usage) — Related Kokiri Forest viewpoint performance drops, but reports a CPU-side bottleneck rather than this issue’s GPU fence-time spike.
Possibly related, for context: - #410 [Performance] Severe CPU-side rendering bottleneck in Kokiri Forest (21–42 FPS, low GPU usage) — Related Kokiri Forest viewpoint performance drops, but reports a CPU-side bottleneck rather than this issue’s GPU fence-time spike.
Author

@BeanIssues Same place, but different analysis. I came to that conclusion through observation from the new FPS counter overlay. It shows huge spikes in GPU fence time. Also, there isn't much difference in CPU utilization between performant and underperforming angles.

That said, I also discovered poor CPU utilization. Not all 8 cores the game uses are fully utilized, and some of them are utilized 100%. There are around 140 threads, but most of them are scheduled to the same processor core.

@BeanIssues Same place, but different analysis. I came to that conclusion through observation from the new FPS counter overlay. It shows huge spikes in GPU fence time. Also, there isn't much difference in CPU utilization between performant and underperforming angles. That said, I also discovered poor CPU utilization. Not all 8 cores the game uses are fully utilized, and some of them are utilized 100%. There are around 140 threads, but most of them are scheduled to the same processor core. <video src="/attachments/de2c0c04-0f43-4160-9043-80cdd3ed08ef" title="Tabby_RKml5UjkzI" controls></video>
Author

@BeanIssues A couple more questions:

  1. Why does the process utilize the last half of the CPU and not the first half, which normally has better production quality? Many game optimization apps change the affinity of background or non-game processes to the last half, with the first half fully utilized by the game.

  2. Is there a way to change the Switch 2's behavior that only use 8 processor cores to use all available cores?

@BeanIssues A couple more questions: 1. Why does the process utilize the last half of the CPU and not the first half, which normally has better production quality? Many game optimization apps change the affinity of background or non-game processes to the last half, with the first half fully utilized by the game. 2. Is there a way to change the Switch 2's behavior that only use 8 processor cores to use all available cores?
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot#1120
No description provided.