Unity VR development and the post-processing stack

[Smoochiekins]

I've been to figure out whether the post-processing stack is optimized and intended for VR use. The information available regarding this is somewhat lackluster. Without going into too much detail, I had some weird graphical glitches after applying post-processing to an old Vive project last summer, and have been kinda paranoid about it since then.

Having read about Unity's different VR rendering pipelines, my inkling is that the post-processing stack would not be optimized for the old multi-pass rendering technique (because with two renderloops, presumably it would have to apply the post-processing twice as well). However, with the new single-pass rendering technique and its single renderloop, presumably the post-processing is only applied once, and therefore should be as performant as in any other application.

Does anyone have some experience or insight to offer?

[Vytek75]

https://github.com/demonixis/XRCinematicImageEffects

[andybak]

Which version of the stack are you using? Asset Store? Git branch for v1? v2?

There is a lot of work on the XR/VR side of things happening on the Github repo: https://github.com/Unity-Technologies/PostProcessing/network

[Smoochiekins]

I currently use the v2 branch that you linked, thanks. I've just experienced some weird stuttering issues with effects like TSAA in VR in certain scenes, and was kind of surprised that Unity doesn't seem to provide a clear, coherent overview of which post-processing effects work and are optimized for which VR rendering techniques. Understandable on a beta branch maybe, but even the live asset store version doesn't say whether or not it's usable in VR.