Below comment refers to issue still present on Quest 2 w/Link. The Rift S is working fine.

Vignette still rendering twice in 2019.4.14 with PostProcessing 2.3.0 and 3.0.1.

unity_VaYl193jfKW3NQ Wow thanks! You saved my day!

Hi, I found a workaround for the VR multi-pass rendering.
https://github.com/noir-neo/PostProcessing/commit/16de98b1aeec2bdd31f12750b14a475e53bf4346

I hope this bug will be fixed formally.

Any update on how to do this? I just tried to unzip their tgz file on the install of Unity, edit the file, zip the folder back up, send the tgz to some website that converts zip to tgz, and replaced that in my local install. I also edited my local which each time I did that would previously have Unity default back to the installer version. This did not work for me. Any other tips?

Hey Strom_Art I been unable to get your fix to work. Any possibility of giving a quick description on how to make this edit? I found the local file but every time I edit it (bloom appears to break when I edit it if Unity is up) and on relaunch, it will come back still broken. Have a lot of emissive objects and a demo on Wed. and hoping to find a solution.

Currently editing the Bloom.shader in my repo\Library\PackageCache\com.unity.postprocessing@2.1.7\PostProcessing\Shaders\Builtins

Any idea how to access the core shader and edit it so each input doesn't get a new edit?

I have reproduced this issue on Unity 2019.2.1f1, using the Postprocessing version [2.1.7], which is dated 2019-06-12.

As there been any progress on this issue? Between this and other postprocessing issues, we've had to disable post processing in our VR project for several months now.

Is postprocessing for vr effectively abandoned for the standard render pipeline? Should we be expecting to migrate to the LWRP for postprocessing support in VR? Any guidance would be appreciated, thank you!

I'm still seeing it on the Oculus Quest.
Sadly the _MainTex_TexelSize.xy fix didn't make any difference for me.

Are there any updates on this or has anyone found a workaround?

Thanks,
Saschka

Hi there! We've been having the same issue here with the bloom where it's been split down the middle of each eye. We managed to solve it by going into Bloom.shader manually by changing every instance of this (about 6 lines):

UnityStereoAdjustedTexelSize(_MainTex_TexelSize).xy

To:

_MainTex_TexelSize.xy

We assume it's 'UnityStereoAdjustedTexelSize' that's causing the offset that messes up the post processing, but that seems to have sorted it out for us and it hasn't broken so far. We're going to try it out on the vignette shader and see if that helps with anything.

Any news about this issue?