Search Unity

  1. Unity Asset Manager is now available in public beta. Try it out now and join the conversation here in the forums.
    Dismiss Notice

PostProcessPass render pass will not execute.

Discussion in '2021.2 Beta' started by Blepius, Jul 6, 2021.

  1. Blepius

    Blepius

    Joined:
    Mar 9, 2021
    Posts:
    68
    Edit: This is an old error for me, I don't remember the details and am unable to reproduce this.

    ---

    Hello,

    I'm receiving this error with no further information after upgrading to the beta. I think the following error is just referring to shaders that were broken during the upgrade, but, how do I find them? Everything looks fine as far as I can see.

    I'm using URP, and have upgraded from 2021.1.10f1 to 2021.2.0b2.

    Missing shader. PostProcessPass render pass will not execute. Check for missing reference in the renderer resources.
    
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
     
    Last edited: Nov 30, 2021
    Blepius, Jul 6, 2021
    #1
    P_Jong likes this.

  2. CodeExc

    CodeExc

    Joined:
    Oct 31, 2016
    Posts:
    8
    Hello,

    do you found a solution? I have the same problem.
    I get the error in a new empty scene. I don't know what resource was broken during the upgrade.
     
    CodeExc, Oct 26, 2021
    #2

  3. sereschkin

    sereschkin

    Joined:
    Mar 8, 2015
    Posts:
    2
    Same. Anyone a solution?
     
    sereschkin, Oct 26, 2021
    #3

  4. Fingerbob

    Fingerbob

    Joined:
    Sep 6, 2014
    Posts:
    24
    Same error (2021.2.0f1). using URP, Android target.
     
    Fingerbob, Oct 27, 2021
    #4

  5. phil_lira

    phil_lira

    Unity Technologies

    Joined:
    Dec 17, 2014
    Posts:
    584
    We are not yet aware of this issue. Could you submit a bug report? We will look at it asap.
     
    phil_lira, Oct 27, 2021
    #5

  6. Fingerbob

    Fingerbob

    Joined:
    Sep 6, 2014
    Posts:
    24
    Bug submitted : Case 1376316

    This one is a wierd one. I've spent a couple of hours trying to clear down to a repro case.

    It's something to do with the URP pipeline settings asset - in the project submitted with the bug report, I have a clean URP asset (newly created in 2020.2.0) and my current project URP pipeline asset (created waaaay back, probably 2019 but possibly 2018). Selecting the "new" URP pipeline asset - no errors. Selecting my "old" URP pipeline asset, and the errors appear (upon loading project, and building, etc).

    It's definitely not as simple as "create a new pipeline asset" to resolve though - I've tried that in my main project, and I'm still seeing the errors.

    Feel free to DM/mail if I can provide any more deets.
     
    Fingerbob, Oct 27, 2021
    #6
    JonasMummSeal and LeonhardP like this.

  7. Oreboat

    Oreboat

    Joined:
    Jul 18, 2020
    Posts:
    5
    It's actually a simple fix, though it needs to be patched out, but just delete original, create a new one, and reassign everything you had in it, once you create a new post process data and reassign it to the render pipeline that should remove the error, or at least it did for me
     
    Oreboat, Nov 4, 2021
    #7

  8. Fingerbob

    Fingerbob

    Joined:
    Sep 6, 2014
    Posts:
    24
    Fingerbob, Nov 17, 2021
    #8
    CodeExc and LeonhardP like this.

  9. peterfnv

    peterfnv

    Joined:
    Mar 20, 2018
    Posts:
    1
    I had this error upgrading Viking Village to 2021.2.2f1. Problem was PlanarReflectionsPostProcessData didn't have a LensFlareDataDrivenPS field and that caused the missing shader error to occur in MaterialLibrary.Load() in PostProcessPass.cs
     
    peterfnv, Nov 22, 2021
    #9
    rgarrett7 likes this.

  10. CodeExc

    CodeExc

    Joined:
    Oct 31, 2016
    Posts:
    8
    Has anyone figured out how to find the broken shaders/files?
     
    CodeExc, Dec 17, 2021
    #10

  11. wheee09

    wheee09

    Joined:
    May 21, 2018
    Posts:
    68
    Wow that was annoying and I wish some of the responses here weren't so callously vague.

    I'll try to be as specific as possible so that other people can be less frustrated.

    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!
     
    wheee09, Jan 27, 2022
    #11
    3dmars, JayroEA, DSivtsov and 14 others like this.

  12. VOTRUBEC

    VOTRUBEC

    Joined:
    Dec 17, 2014
    Posts:
    106
    2021.2.15 -> 2021.2.16 caused the issue for me.

    wheee09's well outlayed solution was spot on and resolved the issue.
     
    VOTRUBEC, Mar 18, 2022
    #12
    CodeFriendlyArt likes this.

  13. beevik_

    beevik_

    Joined:
    Sep 27, 2020
    Posts:
    101
    It seems the URP post-processing data object gets its shader parameters updated every few versions. I just ran into this issue when upgrading from 2021.2.8 to 2021.3.0. The missing shader parameters this time turned out to be scalingSetupPS and easuPS.

    The fix was as wheee09 described above. Remove the existing URP PostProcessData object, create a new one, and update any URP renderers to reference the new one.

    It would be nice if the Unity editor handled updates like this more gracefully.
     
    beevik_, Apr 18, 2022
    #13
    EyeDev44, CodeFriendlyArt, designleviathan and 1 other person like this.

  14. funkyCoty

    funkyCoty

    Joined:
    May 22, 2018
    Posts:
    727
    Just ran into this today too. Deleting our custom one and just using the one URP seems to generate worked for us.
     
    funkyCoty, Apr 20, 2022
    #14
    designleviathan likes this.

  15. designleviathan

    designleviathan

    Joined:
    Jul 24, 2018
    Posts:
    15
    This was me today. Thank you @wheee09 kindly

    As others have mentioend - a small request for Unity to fix editor handling of this.
     
    designleviathan, Apr 28, 2022
    #15

  16. VOTRUBEC

    VOTRUBEC

    Joined:
    Dec 17, 2014
    Posts:
    106
    2022.2.5f and the problem is still there.
     
    VOTRUBEC, Feb 6, 2023
    #16

  17. krunoslavg

    krunoslavg

    Joined:
    Sep 5, 2018
    Posts:
    3
    krunoslavg, Feb 9, 2023
    #17
    sonictimm likes this.

  18. ChinaXue

    ChinaXue

    Joined:
    Apr 12, 2014
    Posts:
    2
    I have solved this problem. The shader referenced in the ScriptableObject of PostProcessData in the project is missing and needs to be re referenced.
     
    ChinaXue, Jun 5, 2023
    #18

  19. EyeDev44

    EyeDev44

    Joined:
    Apr 8, 2017
    Posts:
    149
    Same, after updating Unity to 2023.2.7, post-processing not working
     
    Last edited: Feb 5, 2024
    EyeDev44, Feb 5, 2024
    #19