Game: Stutter in Market - Caused by - Replay thread saturated in Castle Town market with NPCs (~8 ms of 16.7) #1925
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#1925
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 (source 87cb36aa)
Channel
Release
What kind of problem
Low fps or stutter
What happened
In the Castle Town market, with NPCs around the fountain, the game averages 57.6–58.9 fps against its 60 fps target, and about 1 in 8 frames presents late. With the diagnostic switches on, the limit looks like the Vulkan replay thread (78–90% of a core). The GPU is roughly half idle, there's no pipeline compilation during play, and the game's own threads have headroom. Closed-off dungeons run almost perfectly; dips happen in open areas with many NPCs
Steps to reproduce
Expected
A steady 60 fps. The GPU has plenty of headroom and the game's threads aren't saturated.
Actual
Measurements (per 5 s / 600-present window, while circling)
Renderer
GPU
Pipelines
Game threads
Loading
Reading
On this hardware the replay critical path is the limit in busy scenes. Its CPU cost scales with draw count, which matches dips in NPC-heavy open areas while dungeons stay smooth. This isn't GPU, pipeline compilation or the game's own threads, and loading (as in #1831) looks like a minor contributor at most.
Where in the game
Market_Child (child) - Running in a circle around the fountain for roughly 90 seconds
How often
Every time
Graphics card and driver version
NVIDIA GeForce RTX 5070 Ti, NVIDIA 621.01
CPU, RAM and operating system
AMD Ryzen 7 7800X3D 8-Core Processor (16 threads), 31 GB, Windows 11 (build 26200)
Changes from the defaults
DLAA before the bloom: On (default: Off)
Game frame rate cap: Uncapped (default: 60 (the console's))
Fullscreen: On (default: Off)
V-Sync: Off (default: Auto)
Speaker layout: Stereo (default: Auto)
Layout preset: Xbox / PC (default: Nintendo (Def))
Depends on this PC (the values now, not counted as changes):
Quality preset: Custom (default depends on this PC)
Output resolution: 2560x1440 (native) (default depends on this PC)
Profile: Docked (default depends on this PC)
Upscaler: NVIDIA DLSS (default depends on this PC)
Render resolution: Native (DLAA, 2560x1440) (default depends on this PC)
Sharpness: 80% (default depends on this PC)
Window scaling filter: Not needed (window = output) (default depends on this PC)
Game speed: Real time (default depends on this PC)
Frame pacing: On (default depends on this PC)
Switches set (their values are in the attached report.txt): HOS_FPS_LOG, HOS_THREAD_TIMES, LONGSHOT_NO_UPDATE_CHECK, RX_VK_PASS_TIMING, RX_VK_SLOW_LOG.
longshot_log.txt
Log attached
Screenshots or video
Test location image attached
Before you send it
Possibly related, for context: