Game: dark flashing textures, glitched Link, jumpy camera and persistent stutter while in the Kakariko Graveyard (RADV, RX 9070 XT) #1890
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#1890
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?
What happens
Standing in Kakariko Graveyard (entered from Kakariko Village,
Graveyard_Adult), four things start together and do not stop until I leave the area:The same cluster of symptoms happens on the path up to the graveyard in Kakariko Village (matches #1406). Leaving the area recovers it.
Builds it happens on
main6d25da8cbuilt from source, no local changes (pure main),89c3d21+ #1646,So it is base-main behaviour, not caused by any of those PRs.
Ruled out by switch A/Bs
HOS_COLLECT_VECTOR=0,RX_VK_DESC_SPLIT=0,HOS_TEXELS_KEEP_CORE=1,RX_VK_TEX_MOVE=1,RX_VK_WB_MAX_KB=0+RX_VK_WB_DIFF=0,HOS_NATIVE_ZSTD=2,HOS_FPS_STEP=0,RX_VK_MESH_CONV=0. None removes the cluster.Evidence from the logs
vk: texture #883 0x10002fe8e00 3440x1440 NVN 0x34: the GPU wrote its storage (submission 51276): uploaded againvk: upload over a drawn image: #883 3440x1440 … at present 7325 (texture frame 7326), finalized, 0 KB dirty in 0 ranges, a GPU buffer wrote itupload over a drawn imageevents and 40uploaded againevents in one Graveyard run, with 194textures retired.main_cpu240–280 ms per frame,game_msup to 346 ms,main_blockedup to 345 ms, renderer submit/draw in single-digit ms,main_vcore~0.03 ms — i.e. the frame is dominated by the game's own work/waits while the renderer is idle.CRASH: exception 0xc0000005 (read 0x1100, guest 0xfffff00000001100) at /usr/lib/libgcc_s.so.1+0x26617(old base build; not reproduced on pure main in 4 automated round trips).Reproducer
A headless loop built on the repo's control bridge (
scripts/longshot_ctl.py): launch with--profile testand a copied save (starts inGraveyard_Adult), press into play, then teleport Kakariko ↔ Graveyard with the debug teleport; sampleHOS_SLOW_FRAMES,RX_VK_FRAME_TRACE, the log's texture lines, and screenshots after each arrival. No player input needed. Ask and I'll paste the script.Separate regression found on this GPU (not the cause of the above)
#1846 (
RX_VK_MESH_CONV, on by default) removes the vegetation entirely on this machine (RDNA4, no mesh shaders: the game's mesh draws run the compute fallback).RX_VK_MESH_CONV=0brings it back. Reported here because it was found while testing; it is independent of the Graveyard cluster.Environment
CachyOS (Arch), kernel 7.3.1, Mesa 26.3.1 RADV (GFX1201), Radeon RX 9070 XT 16 GB, Ryzen 5 5600X (12 threads), 32 GB RAM, 3440x1440, V-Sync Auto, frame generation off, Threaded rendering Auto (render + recorder threads).
Note on the automated captures
The teleport/dwell captures above come from the repo's control bridge with
--profile test, which setsHOS_HEADLESS=1(offscreen).docs/dev/reference/profiling.mdsays not to take frame-rate numbers from headless/profiled runs, so treat those fps figures as relative signals between builds/settings, not as the in-window fps. The loading re-entry (Sequence_IsLoadingBanc), the texture churn lines, the crash and the screenshots are unaffected by the window mode. A windowedHOS_PROFILE=1run, as performance-report.md describes, is what a maintainer would want for the definitive numbers.Possibly related, for context:
More evidence from an automated dwell in the Graveyard (no teleport, camera turned with the right stick,
longshot-loop --dwellon current main + the PR stack withRX_VK_MESH_CONV=0):control: state play -> loadingand back to play within a frame or two: frames 2477, 2590, 2824, … — with 0.0 draws a frame at the transition and 1819.7 / 2139.0 / 1942.5 draws a frame right after. It looks like the game keeps re-entering its area/scene setup rather than doing one load;ARes_Loading_017%,ARes_Loading_121%,ParallelDecompThread17%,OptimizeChangeBanc17%, while the main thread waits;So the four symptoms line up with the repeated scene re-entry: animation/texture state and camera on each re-entry, plus the frame rate (loaders + replay). No failed/missing asset line is logged (
not found0), and no map change is logged, so it is not a missing romfs file.Area control, same build/run method (
longshot-loop --dwell,RX_VK_MESH_CONV=0): Hyrule Field (adult) 58.2-60.2 fps over four samples with 0state play -> loadingtransitions; Kakariko Graveyard 10-16 fps with loader threads busy andSequence_IsLoadingBancre-entering.HOS_OCB_HOLD_MS=10000removed the extra re-entries in one dwell (only the two teleports remained) but fps stayed 11.8, so the preload hold alone is not the fix. Next:HOS_CHAINacross a Graveyard dwell to name each re-entry wait.Attached the
HOS_PROFILE=1profile of a Graveyard run that ends in the crash (1.4 MB zip): longshot-profile-20261120-194606.zipBuild: current main
6d25da8c+ Tier 1 + #1875/#1810/#941,RX_VK_MESH_CONV=0(vegetation regression of #1846 avoided). The run crashes with0xc0000005during the Kakariko -> Graveyard teleport, as before. Before the crash,report.mdsays:main_blocked_ms(94.8 ms average of a 106 ms stutter); draw translation 3, shader translation 1;trace.json.gz(Perfetto) andspeedscope.json(flame graphs) are in the zip.RX_VK_VRAM_MB=12000was tested too: no difference in fps or retires, so it is not the texture budget.Confirmed fixed by the new build:
v3.0.0-n627-g93e8237d= nightly-627 (afc4d1ad, which already has #792/#936/#1866/#1781/#1809/#1873/#1727/#327/#1646) + #1642 (HOS_BG_THROTTLE, on by default), #1870, #1893, #1914, #1909/#1911 (off), withRX_VK_MESH_CONV=0for the #1846 vegetation regression.In the Graveyard now: steady 60 fps, no loading re-entry, no dark flashes, no Link/camera glitch. The likely contributors are #1642 (the OptimizeChange throttle, on by default) and the now-merged renderer/thread work (#792 image reaper, #1866 recorder parts, #1781/#1809). Closing; reopen if it comes back on a newer base.
Reopening: on
v3.0.0-n631-g67220bf2(nightly-631e0ef1b57+ #1642/#1870/#1893/#1914/#1909/#1911,RX_VK_MESH_CONV=0) the persistent Graveyard/Kakariko state is gone (60 fps, no loading re-entry), but the problem is not fully fixed:So this looks like the residual neighbour-Banc/loading burst rather than the stuck state: #1642 (
HOS_BG_THROTTLE, on) and the merged #792/#1866/#1881 work removed the part that stayed broken. Leaving this open for the transient; next thing to try isHOS_BG_THROTTLEvariants and a windowedHOS_PROFILE=1capture at the moment of the 1–3 s hiccup, now that the PC is available.Deterministic reproducer added: a script that teleports to a map, holds the left stick forward for N seconds and samples the bridge fps between chunks (headless,
--profile test, own save copy). Results on the current build (v3.0.0-n631-g67220bf2= nightly-631 + #1642/#1870/#1893/#1914/#1909/#1911,RX_VK_MESH_CONV=0):The frame trace gives hiccup clusters of 9-12 frames over 0.8-0.9 s, peak frames 240-288 ms in the Graveyard (447 ms in Kakariko) - matching the seen 1-3 s hiccup with the dark flashing textures, which now recovers. Next: A/B
HOS_BG_THROTTLE(default 300:3000 vs 0 vs 100:1000) with this same straight-line run, and a windowedHOS_PROFILE=1at the hiccup.Windowed measurement on
v3.0.0-n679-g0f554e33= nightly-679 (b62932a9, includes #1946 which restores the compute fallback vegetation, #2008, #1933, #2007, #2012, #1574, #1914, #1870) + #1642, #1893, #1909, #2036, #2047. NoRX_VK_MESH_CONVoverride; vegetation is back on default.8 s straight runs, real window (own user dir + save copy):
No sampled fps dip, but the frame trace still shows short clusters of >33 ms frames: 9 frames / 0.83 s (peak 284 ms) and 3 frames / 0.58 s (peak 413 ms) in the Graveyard; 17 frames / 1.13 s (peak 260 ms) in Kakariko. So the remaining 1-3 s hiccup with dark flashes is still there but rarer/shorter. Earlier headless figures were misleading (profiling.md says not to use them for frame rate).
Windowed area sweep on
v3.0.0-n679-0f554e33(nightly-679 + #1642/#1893/#1909/#2036/#2047), own user dir + save copy, 6 s straight run per area, both ages, 18 areas:The run's frame trace (15,299 frames / 266 s, teleport loads included) has 486 frames over 33 ms (3.2 %), worst 1,144 ms, with nine 0.5-1.3 s clusters. Many coincide with the arrival load after a teleport, but the Market-child stretch holds ~51 fps for its whole 6 s instead of 60. Screenshots and the trace are local; happy to attach the trace if wanted.