UE 5.1 Temporal Tremendous Decision ghosting

Can’t declare that I’ve spent lengthy sufficient time to try it out, however I really feel that the ghosting situation of tiny/skinny objects which plagues us in UE 5.0 with Temporal Tremendous Decision AA is definitely getting worse in 5.1.

“Responsive AA” in Materials-Translucency-Superior not works in 5.1, however then even in 5.0.3 it solely works on translucent materials. Tiny/skinny opaque object with out this feature undergo the same ghosting situation, albeit to a lesser diploma.

UE 5.0.3:

UE 5.1.0:

Inexperienced: Niagara Default Sprite Materials (additive, responsive AA);
Pink: Related additive materials with out responsive AA

I’m kinda tempted to report this as a bug to Epic, however I’d like to listen to from different’s like Niels if you already know any repair or workaround.

I’m fairly certain they modified the speed collect step trigger they advised me it’d get higher. Perhaps there’s nonetheless a small oversight although.

I’ll see if I can test later

Should you render After dof, which is the place you’ll wish to render the overwhelming majority of your vfx anyway, tsr ghosting appears to have been resolved virtually utterly, in order that’s tremendous good.

Earlier than dof appears to sadly be a totally totally different story. Even with output velocity, small particles will nonetheless ghost when the vary by which movement might be discovered is simply too small.

Masked appears to have improved just a little bit. However tremendous small particles will nonetheless create points.

Altering materials move to ‘After Movement Blur’ as a substitute of ‘After DoF’ appears to resolve all the brand new ghosting points for me in 5.1

Really Niagara Default Sprite Materials is already utilizing “After DoF” move.
/Script/Engine.Materials’/Niagara/DefaultAssets/DefaultSpriteMaterial.DefaultSpriteMaterial’
However the “UE 5.1” challenge video I recorded earlier is definitely migrated from an initially UE 5.0.3 challenge. The ghosting doesn’t go away nonetheless I attempted to vary the DoF move and Output Velocity settings.

After creating a brand new UE 5.1 challenge from scratch, the ghosting is gone when “Output Velocity” in Materials – Translucency is disabled, in any other case you could disable “Movement Vector Setting” in Niagara Renderer as a substitute. “Responsive AA” is seemingly doing nothing in any respect. The seen distinction is simply too onerous to inform.

IDK if one thing must be up to date within the ini manually to allow the ghosting elimination after I simply migrate my older challenge to five.1.

One quirkiness in Epic’s Content material Examples challenge opened in 5.1 is that if I take advantage of “After Movement Blur” move, the brightness of the small particle is completely totally different, and the article ignores depth as if “Disable Depth Take a look at” is enabled, although it’s really disabled.

Edit: The surprising ignore depth take a look at can also be true in a newly created 5.1 challenge. I assume that is certainly a bug?

Venture Settings → Rendering → Translucency → Activate Separate Translucency.
Materials Particulars → Activate Responsive AA and Translucency Cross set to After DOF.

I attempted what everybody else instructed and it wasn’t working for me. It was solely after turning on Separate Translucency that this labored.
Hope this helps

You may actually management the Movement Blur being utilized to particles on a per particle foundation.

• Allow after DOF and output Velocities within the materials.
• Then inside your Niagar System, change the Movement Blur settings to Approximate:
• Create a vector parameter, in my case I known as it ‘MotionBlur’. Set it to Velocity * customized float (in my case a Person Parameter).
• Change the VelocityBinding in your Rendererer with the newly created MotionBlur parameter.
• You may then management the quantity of MotionBlur being utilized by adjusting the parameter.

Nevertheless, I’ve discovered this give combined outcomes. With out movement Blur/Velocities being utilized, small particles simply get misplaced, visually. It’s a trade-off and simply doesn’t fairly work completely more often than not. It would additionally rely in your background, e.g. noisy background will give worse outcomes than clear sky.
You may all the time attempt to set the MotionBlur to ‘Disable’ as nicely.

On a aspect observe, the newly ‘After MotionBlur’ move is ineffective 99% of the time. As partices attract bizarre sorting order in comparison with the remainder of the scene. Unsure what that is meant for use for in apply.