Search Unity

Bug Compute shader (materialflags): Property (_GBufferTexture2)at kernel index (0)

Discussion in 'High Definition Render Pipeline' started by JJRivers, Sep 28, 2021.

  1. JJRivers

    JJRivers

    Joined:
    Oct 16, 2018
    Posts:
    137
    The error message:
    Code (CSharp):
    1. Compute shader (materialflags): Property (_GBufferTexture2) at kernel index (0) is not set
    2. UnityEngine.Rendering.RenderPipelineManager:DoRenderLoop_Internal (UnityEngine.Rendering.RenderPipelineAsset,intptr,System.Collections.Generic.List`1<UnityEngine.Camera/RenderRequest>,Unity.Collections.LowLevel.Unsafe.AtomicSafetyHandle)
    appears intermittently when opening a project in 2020.3.11f1 through 2020.3.19f1.

    Nothing seems to break and i'm assuming it's simply the GBuffer not being ready for rendering while the editor is already attempting to render, but is this actually the case or is this a bug. If it's benign this should probably be suppressed immediately before first render?
     
  2. JJRivers

    JJRivers

    Joined:
    Oct 16, 2018
    Posts:
    137
    Bumping this up, we have presumed this to be an editor only error since to date it only ever pops up when opening editor without scene view open.

    Now however we've seen an incident of this showing up in a build and getting some clues as to the cause would be nice. Any @Unity folks care to list some of the thing's you'd need? (the entire project is rather unfeasible practically speaking)