Bug Post Processing TAA broken with Multi Pass

Using
U 2020.3.8
PP 3.1.1
OpenXR 1.2.0
XR Mngmnt 4.0.5

when using TAA with Multi Pass and deferred the right eye renders incorrectly.

 

I also see this, submitting a repro project now. FXAA is also broken.

https://issuetracker.unity3d.com/is...iasing-is-used-with-multi-pass-rendering-mode

 

I noticed other PP effects are broken as well with OpenXR, have submitted another project. Hopefully the issues are related.

https://issuetracker.unity3d.com/is...sing-postexposure-effect-has-visual-artifacts

 

Why has this received no attention for almost a whole year now? TAA is absolutely essential for visual quality in VR, there really is no substitute for it. MSAA & FXAA / SMAA is going to have horrendous specular aliasing on PBR materials and supersampling is too costly for any realistic performance goals.

Using single pass is not an option for developers who depend on multi pass only shaders, and there are no third-party TAA assets that support multi pass either.

Is this just going to get swept under the rug? Is there some reason this can't be fixed? Why is this not a priority issue? I would really appreciate some communication from the Unity team.

 

Yeah would be good if Unity could acknowledge this issue. TAA is definitely badly broken right now in VR multi pass and it's a huge problem for us as we have failed to find an alternative suitable AA method.

Unity: 2020.3.35f1
PP: 3.2.2
OpenXR: 1.4.2

 

Huge issue. Please fix it Unity!

 

Not only is there still no communication, but now to the tracker page is also gone: https://issuetracker.unity3d.com/is...iasing-is-used-with-multi-pass-rendering-mode

EDIT:

After submitting another bug report it turns out the the issue still exists on the tracker, but it was renamed and doesn't show up when your search for TAA for some reason. This is the new link: https://issuetracker.unity3d.com/is...iasing-is-used-with-multi-pass-rendering-mode

There also is a new label "Planned for 3.2.X" now, looks like it's finally being worked on!

 

It looks like they've been working on it for years and nothing changes. Just like with the rest of the bugs.

BUMP.

 

Now it's no longer "Planned' and instead "Under Consideration" for 3.2.X. That sounds like a step back to me, can someone from the Unity team please clarify what this change means?

I would hugely appreciate some information on what timescale we can expect for fixes in built-in post processing, if this is still so low priority that it might take another year I will reluctantly start looking for other solutions. I really want to stick with Unity, but the HDRP is just too CPU heavy and custom shader unfriendly and the URP still doesn't have any TAA.