Ghosting with new Volumetric Clouds Render Target Mode

Hi, we’re wanting to use r.VolumetricRenderTarget.Mode=3 in our project, but it’s causing some major ghosting issues.

This is the same as having GetMainDownsampleFactor() returning 2, and GetTraceDownsampleFactor() returning 4, in VolumetricRenderTarget.cpp.

i.e. Trace 1/8th resolution, Reconstruct 1/2 resolution

Mode 3 is pretty similar to Mode 0, and if we change it so that it matches Mode 0, and returns 2 for GetTraceDownsampleFactor(), the problem goes away. But we don’t want to do that since we’d essentially be using Mode 0 under a different name and have that same increased performance cost.

How can we solve this ghosting problem another way?

Using r.VolumetricRenderTarget.ReprojectionBoxConstraint 1 does improve the ghosting so it’s not as dramatic.