VRAM: alias the DLSS-RR input set with lighting scratch (300-400 MB) #1429
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#1429
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?
The RR input set (50 B per render pixel, llcleandlssrrvk.cpp ~196-215, ~396 MB at 4K DLAA) is first written after lighting, while lighting scratch is dead by pass 2. Aliasing needs a 3+ phase arena (RenderVKAliasTargets is two phases, images only). Risks: the RR guide pass reads the G-buffer and mDsRtTrace; GI-lag mode overlaps GI with the DLSS resolve; async compute joins; VR per-view sets. Low confidence -- needs the real pass order traced in recordFrame.
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.