Game: Repeatable frame spikes when enemies die in Hyrule Field (RTX 5080, Linux) #1213
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#1213
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?
Reported on Discord
Longshot version and channel
nightly-363-0cab3548, nightly (from
longshot_log.txt).What happened and steps
The reporter loaded a save in Hyrule Field, killed several enemies, changed to night, then killed more enemies (skeletons). Each time an enemy died, repeatable frame spikes occurred. Hyrule Field was otherwise smooth.
Where in the game
Hyrule Field, while killing enemies, including skeletons at night.
How often
Reported as repeatable, occurring as soon as an enemy dies.
Graphics card and driver version
NVIDIA GeForce RTX 5080. The reporter gives driver as “620”; exact driver version unknown. The new log identifies Vulkan driver ID 0x9b118180 but does not clarify the user-facing driver version.
CPU, RAM and operating system
AMD Ryzen 7 9800X3D, Linux. The log reports 31,186 MB system memory; OS distribution/version and exact RAM amount remain unknown.
Logs and performance capture
Two supplied
longshot_log.txtfiles. The latest reports 3840×2160 output. It contains general frame/replay timing statistics, but lacksHOS_THREAD_TIMESandRX_VK_PASS_TIMINGmeasurements required by the performance-profile procedure, so it does not isolate the reported spikes. FPS samples: 61 total, minimum 43, median 60, maximum 120; no sample is far below the median.Still needed
A performance profile captured during the enemy-death spikes, with
HOS_FPS_LOG=1,HOS_THREAD_TIMES=5,RX_VK_PASS_TIMING=1andRX_VK_SLOW_LOG=50configured as described at https://longshot.magicbean.dev/help/performance/; exact NVIDIA driver version; OS distribution/version; RAM amount; graphics settings (preset, render resolution, upscaler, frame generation, V-Sync); and confirmation of spike magnitude/frequency. The reporter should capture the same Hyrule Field enemy-death scenario, then send the resulting Bug report folder andlongshot_log.txt.Possibly related but not confirmed to be the same symptom: #1111 tracks broader stuttering across the map, worst in Hyrule Field and Death Mountain on an RTX 4090. This report is specifically repeatable spikes when an enemy dies on Linux with an RTX 5080. PR #363 documents another Hyrule Field slowdown and profiling A/B plan, but it is documentation only and does not establish a fix for this enemy-death symptom.
Files from the Discord report:
Updated with more from Discord: Added the second log review and clarified that it lacks required profile measurements; noted related Hyrule Field profiling documentation is not a fix for this symptom.
Files:
From Discord:
The reporter supplied another
longshot_log.txt(nightly-363-0cab3548). It still does not containHOS_THREAD_TIMESorRX_VK_PASS_TIMINGprofile measurements, so it does not provide the requested performance profile. It reports 3840×2160 output and frame-rate samples of min 44, median 60, max 122; these general samples do not isolate enemy-death spikes. The log identifies RTX 5080 and Ryzen 7 9800X3D; system memory is reported as 31,186 MB. The reporter asks whether the capture is correct; it is not sufficient to diagnose the specific spikes.