Repository navigation
radiance: feed the cache from the indirect raygen and reuse it on the second bounce - #93
Merged
Merged
Conversation
This was referenced Nov 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The indirect raygen stores the first-bounce
hitRadianceathitSurf.positionand the second diffuse bounce (GI level 2) reuses a stored cell instead of running its NEE, so screen-space hits and the volume probes share one world cache.Runtime e1m1,
rt_gi_level 2, split, 30 dumps: cache off[69.41, 42.47, 34.52](0 hits) vs on[65.78, 36.93, 29.29](11,337,693 hits, 20 misses, 876 active), image diff 6.3, 0NVRHI::ERROR. The cache is active end to end; the ~8% darkening is the first-slice approximation of reusing the stored outgoing radiance for the second bounce (the cache stays opt-in).