Kokiri Forrest unusual GPU fence time in certain camera angle #1120
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#1120
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
Possibly related, for context:
@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 A couple more questions:
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.
Is there a way to change the Switch 2's behavior that only use 8 processor cores to use all available cores?