I've updated the property names so we don't break compat, but I kept the UI label the same. We can change it once jittered soft shadows land.
Can you try noise_function(g_data.P + noise_offset); then?
That can cause troubles on planes that are aligned "just in the right way", and probably in other cases.
Using the noise_offset as…
But I wonder if we really need this property. EEVEE legacy didn't refresh the transparent shadows in the viewport at all if soft shadows were disabled.
I think it's needed, otherwise we're…
I tried all your suggestions and it still shows the same issue.
I don't think it's an issue with fract(rand + offset), but simply that the correlation between front and back layers stays the…
Oh... because the horizon scan is driven by the AOData from the AmbientOcclussion module.
But these new properties are added to RayTraceData directly.
I find that quite confusing, TBH.
I only took a quick look at the code, but I've tested the patch on my RTX GPU and on my cheap integrated AMD laptop and the quality and performance are better on both.
Just a nitpick, but I would make clear that this also has a render time cost, not only a memory cost.
Why are you using the gtao term for the DNA property?
There are some functions duplicated between the denoise and resolve shaders.
The force push doesn't contain any change. I just reverted the last 3 commits, since I've pushed them here by error.
I ended up using pcg4d since we have to take the sample offset into account and doing fract(hash + noise) was giving pretty bad results for some reason:
![imagen](/attachments/14da9e5e-9fdb-4d…