Graphics.ExecuteCommandBufferAsync with ComputeShader calling UpdateRendererBoundingVolumes

When I use

Graphics.ExecuteCommandBufferAsync

to dispatch a compute shader, I get a call to

UpdateRendererBoundingVolumes

before actually dispatching the shader on the render thread.


The first

MeshInstancedRenderer.LateUpdate()

here calls

Graphics.ExecuteCommandBufferAsync

and you can see there are multiple calls before the actual internal call to

ComputeShader.Dispatch

. The following instances however don't get this and take no time to dispatch.

What causes this? Is there a way to stop it? I've had to go back to just calling

ComputeShader.Dispatch

 

@SLGSimon
Did you figure out what was causing the problem?

 

Nope, but I assume it has something to do with https://unity.com/how-to/best-practices-performance-optimization-unity#transforms

 

Did anyone get a solution to this? Seems like a pretty big issue. Makes async compute not really usable for us

 

I don't think I opened an issue with Unity for it, so probably a good idea to if you can.

 

Bump

 

Any news?

Problem/Bug is still there and I couldn't find any reason why UpdateRendererBoundingVolumes should be called when computing done isn't related to any bounding volume.