CommandBuffer methods don't run properly inside of render feature

Unity Engine
, , , ,
1

Pulling my hair on this one, I have a render feature where I want to draw meshes in a custom order, so I’m running CommandBuffer.DrawRenderer(). Which works fine, but I cant set or change render targets. For example, adding this line in Execute():

buffer.SetRenderTarget(new RenderTargetIdentifier[]{ BuiltinRenderTextureType.CameraTarget, _depthLUT }, BuiltinRenderTextureType.CameraTarget);

does nothing. The shader fragment is writing to SVTarget0 and SVTarget1. But adding this line makes no difference. Even changing it to:

buffer.SetRenderTarget(new RenderTargetIdentifier[]{ _depthLUT, _depthLUT }, BuiltinRenderTextureType.CameraTarget);

does nothing, _depthLUT remains black and DrawRenderer works as normal, rendering to the screen. Any idea why this is happening? I’d like to render some stuff on a secondary texture.

Unity 2021.3.15 LTS, URP 12.1.8

2

Try using the “ConfigureTarget” function, by overriding the Configure function in your render pass. By design, the render target must be set here.

9004846--1240888--upload_2023-5-10_16-59-55.png

9004846--1240876--upload_2023-5-10_16-57-17.png

3

Out of interest, do you know where it says this in the documentation? I’ve heard it said before on the forums but I can’t find the doc reference.

OP:
buffer.SetRenderTarget(int) and (RTHandle) work fine for me on 2019, 2020, 2021, and 2022, including the optional versions where depth is specified.

e.g.

buffer.SetRenderTarget(_OutlineObjectBuffer);
context.ExecuteCommandBuffer(buffer);
CommandBufferPool.Release(buffer);
// make sure you execute the buffer before using context.DrawRenderers
context.DrawRenderers(renderingData.cullResults, ref drawingSettings, ref filteringSettings);
4

I have already tried that in a similar way:

ConfigureTarget(new RenderTargetIdentifier[]{ BuiltinRenderTextureType.CameraTarget, _depthLUT });

and also:

ConfigureTarget(new RenderTargetIdentifier[]{ _depthLUT, BuiltinRenderTextureType.CameraTarget });

where _depthLUT remained black and it just rendered to the camera target.

However, when I tried:

ConfigureTarget(_depthLUT,);

It renders correctly to the _depthLUT target, without showing anything on the screen. So I’m not quite sure why this is happening. For info, this is what the frag shader that is used to render looks like:

            struct PixelS
            {
                float4 target0 : SV_Target0;
                float4 target1 : SV_Target1;
            };
           
            PixelS SpriteFrag(v2f IN) : SV_Target
            {
                PixelS val;
               
                fixed4 c = tex2D(_Main, IN.texcoord);
                fixed4 d = tex2D(_Sec, IN.texcoord);
              

                val.target0 = c;
                val.target1 = d
               
                return val;
            }

target0 shows as normal.

5

We’ve probably read the same forum posts :stuck_out_tongue: To which I’m clenching in absence of any concrete explanation. The C# function summary does say the same thing. I believe If ConfigureTarget isn’t used, URP assumes you’re targeting the current camera color target, which may have some adverse effect. I suppose it doesn’t hurt to be explicit.

In the same pass where I was looking, I actually also use CommandBuffer.SetRenderTarget in the Execute function, and that works perfectly.

The key may be to execute+clear the command buffer right after doing so for it to work (like you have as well).

1 Like
6

Hmm not sure what could cause it then, such a pain. Can you share how you set up the _mrt array?

7

Tried a multitude of combinations, it seems SetRenderTarget() works properly for a single color target, but when an array is given it always resets to the default single camera target, no matter what combinations. This seems like a bug.

1 Like
8

I can report it also works when setting a color target and a depth target (both RenderTargetIdentifier or RTHandles). I have not used the array functionality before though.

9

Yes works with that as well, but not with color[ ]. I just tested in a fresh project and it doesnt work in that either

1 Like