Search Issue Tracker

Fixed in 2.3.1



Found in [Package]


Issue ID




[XR][Post Processing] 'Directly to Camera' Post Processing mode causes black screen with the builtin renderer and XR

Package: PostProcessing


How to reproduce:
1) Create a new project.
2) Enable VR.
3) Install the Post Processing package
4) Setup post processing in the scene.
5) Build and run.

Expected Results: Post processing is applied correctly in both eyes.
Actual Results: Black screen.

Package Version: 2.1.2, 2.1.3, 2.1.5, 2.1.7
Reproducible in: 2019.1.0b9, 2019.1.0b3, 2019.1.0b7, 2019.1.0f1, 2019.2.0b7, 2019.3.0a1
Not reproducible in : 2018.3.11f1

Occurs with DirectX11 and OpenGLCore, when all stereo rendering modes, all combinations of HDR/MSAA/Color space, with Oculus, OpenVR, and MockHMD.
Only occurs with the legacy renderer and Directly to Camera Target option enabled. LWRP is unaffected by this issue. Monoscopic is unaffected by this issue.

Comments (6)

  1. Giantbean

    Nov 14, 2019 22:09

    Updated to 2019.2.2f1 and this is happening. When Directly to Camera is unchecked the screen is no longer black but everything is blurry and any post process effects render dependent to each eye (VR) in such a way that it creates artifacts in the center of view.

  2. r1239104

    Sep 09, 2019 17:43

    Disabling "Directly to Camera Target" in Post Process Layer removes the black screen but causes the render to be blurry.

    Please consider making this a priority as it is a show-stopper for upgrading VR projects to 2019.

    Related thread:

  3. MrFigment

    May 30, 2019 15:16

    There is a "fix" for now... disable the "Directly to camera target" checkbox in "Post Process Layer"

    I'm using unity 2019.1.4 with Oculus Rift

  4. BlindMystics-P3TE

    Apr 17, 2019 08:02

    Found to also occur in 2019.1.0f2
    Quite unfortunate that this has made it out of the beta into the full release.

    > Using OpenVR on a HTC Vive.
    > Post processing does not have any issues in 2018.3.12f1

    Additionally, based on that the fact that this occurs in 2018.3 means that this issue should probably be marked as a regression.

  5. Chootin

    Apr 17, 2019 08:01

    This bug occurs when running the game in the editor as well as a build.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.