VRAM: legacy avatar RT data (~3 GB) is dropped all-or-nothing at ladder rung 22 #1424
Labels
No labels
amd
avatars
bug
builder
cannot-reproduce
crash
epic
feature
from-viewer
gl-removal
known-limitation
monitoring
parity
perf
platform
priority
critical
priority
high
priority
low
priority
medium
provenance
rendering
rt
status
in-progress
status
testing
status
up-next
triage
ui
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sky_line/Slipstream#1424
Loading…
Add table
Add a link
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?
Legacy avatars' RT data -- per-avatar-group rig BLAS built FAST_BUILD + ALLOW_UPDATE with no compaction (llcleanrtvk.cpp ~3150-3250) plus a 16 B/vertex RT position copy mRigPos (llcleanrtvk.cpp ~184, 2905) -- measured ~2,900-3,070 MB in #1422's log ("legacy avatars (rigged meshes + worn attachments) dropped from RT (2972 MB)"). The ladder only releases it at rung 22 ("avatars in RT"), all at once, after textures, mesh LOD and draw distance were already cut.
Do: compact rig BLAS where they are stable (or build compacted for far avatars), decimated RT copies for far avatars, and a partial farthest-first drop that runs before any content rung. Log the split of the figure into BLAS / rig copy / scratch. Estimated recoverable 900-1,800 MB (COMPUTED guess, medium confidence).
From the 4K VRAM audit (2026-11-04) prompted by #1422 (RTX 4070 Ti SUPER at 3840x2089 with RT + GI: the degrade ladder sat at rung 21/45, capping textures, mesh detail 1/4 and draw distance 35% while lighting kept full cost). Sizes are at 4K unless noted; COMPUTED = from formats in code, MEASURED = from logs.