Search Issue Tracker

Fixed in 14.0.2

Votes

8

Found in [Package]

12.0.0

Issue ID

1376316

Regression

Yes

"PostProcessPass render pass will not execute" error thrown in Console when upgrading URP

Package: Scriptable Render Pipeline Universal

-

How to reproduce:
1. Create an empty 3D project
2. Navigate to "Window" - "Package Manager" and install the Universal RP package from "Unity Registry"
3. Drag and drop files from "VisualiserURP.zip" (with ".meta" files) to the projects "Assets" folder
4. Have Game View open and navigate to "Edit" -> "Project Settings..." -> "Graphics" and set "VisualiserUniversalRenderPipelineAsset" as Pipeline Settings

Expected result: No errors are thrown in Console
Actual result: "Missing shader. PostProcessPass render pass will not execute. Check for missing reference in the renderer resources." error thrown in Console

Reproducible with: 12.0.0, 12.1.1, 13.1.0 (2022.1.0a10, 2021.2.3f1, 2022.1.0a15)
Not reproducible with: 7.7.1, 10.7.0, 11.0.0 (2019.4.32f1, 2020.3.23f1, 2021.1.28f1)

Notes:
1. Error seems to have no actual consequences
2. Simple deleting ".meta" files and recompiling fixes the issue
3. Ensure that you have a Game View as well as the Project Settings window open as sometimes the errors do not occur if they are not open

  1. Resolution Note (fix version 14.0.2):

    Fixed in: 2022.2.0a12

Comments (4)

  1. nathan2019spence

    Oct 03, 2022 20:55

    I was downloading their addressable example for LoadyDungeons and recieved the error message, version number Unity 2021.3.2.2f I ended up going to Assests / Rendering in the project section and in the Inspector I unchecked post processing and all the errors went away.......Lost about 2 hours trying to make the error go away...

  2. gotiobg

    Mar 24, 2022 18:02

    I was using the Render Pipeline from the Viking Village asset. It seems the post-processing of that asset got corrupted and it showed me two error messages "Missing shader. PostProcessPass render pass will not execute. Check for missing reference in the renderer resources." every time I started Unity or ran the game through the editor play button.
    I fixed it by setting the Render Pipeline to URP-Performant. I guess Balanced and High-Fidelity work too.

  3. wheee09

    Jan 27, 2022 18:30

    I had generated a "CustomPostProcessData" in a previous version (this can be done via Create -> Rendering -> URP Post Processing Data). In my case, I wasn't even using it, but it looks like it's corrupted/not-migrated-properly so I ended up removing it and creating a new one.

    Then follow these steps:
    - Go to your Render Pipeline asset
    - Go to each one of your Renderers in the Renderer List
    - Disable Post-Processing (for now and this may not be necessary)-
    - Once done, you shouldn't see anymore errors
    - Go back and enable Post-processing and select the **newly** created "CustomPostProcessData" asset. If you select the old one (instead of removing it) you'll see those pesky errors again.
    Hope that helps!

  4. morepixels

    Nov 20, 2021 17:32

    > 2. Simple deleting ".meta" files and recompiling fixes the issue
    .meta files of which assets?

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.