Bug Render Graph Execution error at pass Volumetric Clouds Ambient Probe

How to fix such a bug? The game window works fine, but the scene window just has a black screen

 

I am getting the same thing when viewing my scene which includes volumetric clouds in Scene View.

For me, In Game View and in Build/Editor Play these errors do not appear and everything renders and these errors do not appear.

 

Well, I just found that by toggling the lighting control in scene view the error goes away. Cant view the scene without lighting it seems.

 

That doesn't work for me. :-/

 

I'm getting this issue in version 2022.1.11f1.3452, (thanks azcoffeehabit toggling the lighting control stops it happening). Happens on some machines and not others.

 

Actually sorry this is a different error, I misread original post. I get spammed with the following when I enter the prefab editor.

Code (CSharp):

1.  
2. Render Graph Execution error at pass Uber Post (26)
3. UnityEngine.GUIUtility:processEvent (int,intptr,bool&)
4.  
5.  
6. InvalidOperationException: Trying to use a texture (CameraColor) that was already released or not yet created. Make sure you declare it for reading in your pass or you don't read it before it's been written to at least once.
7. UnityEngine.Experimental.Rendering.RenderGraphModule.RenderGraphResourceRegistry.GetTexture (UnityEngine.Experimental.Rendering.RenderGraphModule.TextureHandle& handle) (at Library/PackageCache/com.unity.render-pipelines.core@13.1.8/Runtime/RenderGraph/RenderGraphResourceRegistry.cs:114)
8. UnityEngine.Experimental.Rendering.RenderGraphModule.TextureHandle.op_Implicit (UnityEngine.Experimental.Rendering.RenderGraphModule.TextureHandle texture) (at Library/PackageCache/com.unity.render-pipelines.core@13.1.8/Runtime/RenderGraph/RenderGraphResourceTexture.cs:32)
9. UnityEngine.Rendering.HighDefinition.HDRenderPipeline+<>c.<UberPass>b__953_0 (UnityEngine.Rendering.HighDefinition.HDRenderPipeline+UberPostPassData data, UnityEngine.Experimental.Rendering.RenderGraphModule.RenderGraphContext ctx) (at Library/PackageCache/com.unity.render-pipelines.high-definition@13.1.8/Runtime/RenderPipeline/HDRenderPipeline.PostProcess.cs:4741)
10. UnityEngine.Experimental.Rendering.RenderGraphModule.RenderGraphPass`1[PassData].Execute (UnityEngine.Experimental.Rendering.RenderGraphModule.RenderGraphContext renderGraphContext) (at Library/PackageCache/com.unity.render-pipelines.core@13.1.8/Runtime/RenderGraph/RenderGraphPass.cs:151)
11. UnityEngine.Experimental.Rendering.RenderGraphModule.RenderGraph.ExecuteCompiledPass (UnityEngine.Experimental.Rendering.RenderGraphModule.RenderGraph+CompiledPassInfo& passInfo, System.Int32 passIndex) (at Library/PackageCache/com.unity.render-pipelines.core@13.1.8/Runtime/RenderGraph/RenderGraph.cs:1337)
12. UnityEngine.GUIUtility:processEvent(Int32, IntPtr, Boolean&)
13.  
14.  
15. Render Graph Execution error
16. UnityEngine.GUIUtility:processEvent (int,intptr,bool&)

But turning on scene lighting does stop it.

 

I'm not sure if i read correctly, but i can say, something simliar happens to to me all the time in the HDRP stuffs. Whenever i switch mode to 2d ui, just constant flickering color (seemingly from the light source maybe? shrug) Very frustrating trying to work on ui with constant flickering color background. And if i try and dare turn off the lights, blam, shader graph error galore spams the editor. This is not any one project in particular, it 'reproduceable' in 'every project'. lol


In my case, it gets extreme though. When trying to edit a 2d ui text field (without the clipping disabled, it just goes to town with the flicker fest.) I dunno.... shrug, Unity, heh.

I did find a hacky work around though , by disabling the scene view camera dynamic clipping, it supressed the really wild flickering color while i work on my ui stuffs.

 

Hi,

I had same error. Blank scene window and bunch of same error messages as in the first post.

I toggled the "scene lightning is used" -button in the scene window and the error messages stopped. Haven't yet test out extensively, but works for now.

Br, Jukka