GI re-shade: add a significance test and find why ~25 lights count as changed every frame #980
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#980
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?
From the 2026-10-23 GI performance pass. Baseline: RTX 5090, 4K, DLSS Ultra Performance (1280x720 render), GI at full render resolution, GI 3 + cache, ReSTIR DI 3, emissive on: GPU 30.9 ms/frame (GPU-bound), async deferred lighting 20.1 ms,
c_gi_trace12.7 ms (883k rays/frame).0.235 re-shades per GI ray (about 1-2 ms). Each re-shade is a full closest-hit ray plus hit shading.
giChangedReacheshas no significance test: any changed light in range with attenuation above 0 triggers it, and about 25 of 256 lights count as changed every frame at steady state.Plan
RenderVKReSTIRFlickerEpstoo tight? lights on avatars?).Estimate
1-2 ms, small effort, risk: a slightly stale tint in rare cases.
Fixed in 1.5.0 Beta 1 (
80b05090e5). Reopen if you still see it.