Custom TAA solution "broke" when upgrading to 2017.1... We can't find the issue.

We recently upgraded to 2017.1 and everything went pretty smooth, but our custom TAA solution is now showing visible jittering from moving the projection matrix, while it wasn’t visible in 5.6 before.

We haven’t been able to find anything regarding changes to this logic in the release notes, and we’re having a really hard time tracking down what is actually causing the issue.

One thing we tried to do for fun was set up the same project in both 5.6 and 2017.1 and get a motion vector readout from it. In 2017.1 the jittering is actively visible in the motion texture, while it’s not in 5.6.

Here’s a gif showing them side by side: Imgur: The magic of the Internet

If anyone knows what might be going it’d be really appreciated if you’d share.

That’s not what he said. He didn’t buy an asset. They have their own TAA solution, which stopped working properly recently due to something Unity changed, which they are not sure what it is.

1 Like

Yeah it has nothing to do with Livenda and their asset, don’t mind the name. I’m just curious about what Unity changed in regards to the projection matrix, since even their own post stack seems to have some weird jittering issues, but with directional shadows being really jittery when applied?

I’m not really sure where to look for a solution to this, and the 2017.1 changelog doesn’t mention any changes being made to the projection matrix.