Foliage WPO Velocity for TAA smearing

[Chosker]

@Guillaume.Abadie

Sorry for the delay in my response as I needed a last minute break for personnal reasons.

no worries

@Guillaume.Abadie

r.TemporalAA.Algorithm=1’s history rejection no longer need to differentiate dynamic geometry from static geometry in the velocity buffer that r.PostProcessAAQuality=4’s AA_DYNAMIC_ANTIGHOST need. So r.BasePassForceOutputsVelocity=1 would basiaclly make Gen4 TAA exactly like r.PostProcessAAQuality=3.

So using 4.26’s r.BasePassForceOutputsVelocity=1 when you have r.TemporalAA.Algorithm=1 or r.PostProcessAAQuality=3. Not that r.BasePassForceOutputsVelocity=1 only work when r.BasePassOutputsVelocity=1. the performance overhead r.BasePassForceOutputsVelocity=1 is negliegable on base PS4 and base XB1 and more powerful hardware thaw, due to the BasePassPixelShader.usf already compiling all the math to compute the velocity and just outputing black when the geometry is static.

In case needed, there is a feedback forum thread about Gen5 TAA hereI’m trying to remain as active as possible if you feel like talking/give feedback more about Gen5 TAA.

so if I get it right, on 4.26 using the following settings together:

r.TemporalAA.Algorithm=1 -or- r.PostProcessAAQuality=3
r.BasePassOutputsVelocity=1
r.BasePassForceOutputsVelocity=1

… should compute proper velocity from WPO, ultimately getting rid of WPO ghosting?
I’ll have to give it a proper try then!