You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the ExecuteIndirect example the SceneConstantBuffer argument is defined as INDIRECT_ARGUMENT_TYPE_CONSTANT_BUFFER_VIEW. Intuitivly I would think that in the IndirectCommand structure the CBV needs to be of type D3D12_CONSTANT_BUFFER_VIEW_DESC which consists of the BufferLocation and its SizeInBytes.
So why does it work? And is there any documentation to make clear which indirect argument buffer structure needs to be used for which indirect argument type? My search so far didn't give me any answers.
Also there is no documentation which union fields need to be set in D3D12_INDIRECT_ARGUMENT_DESC for which type.
I would find it helpful to have a table in the docs like this:
Hey there,
maybe I get something fundamentally wrong but the documentation does not say anything about which indirect argument buffer structure needs to be used for which indirect argument type in the IndirectCommand structure: https://learn.microsoft.com/en-us/windows/win32/direct3d12/indirect-drawing
In the ExecuteIndirect example the SceneConstantBuffer argument is defined as INDIRECT_ARGUMENT_TYPE_CONSTANT_BUFFER_VIEW. Intuitivly I would think that in the IndirectCommand structure the CBV needs to be of type D3D12_CONSTANT_BUFFER_VIEW_DESC which consists of the BufferLocation and its SizeInBytes.
But in the example only a D3D12_GPU_VIRTUAL_ADDRESS is used in the IndirectCommand structure to give the buffer location without the size.
So why does it work? And is there any documentation to make clear which indirect argument buffer structure needs to be used for which indirect argument type? My search so far didn't give me any answers.
Also there is no documentation which union fields need to be set in D3D12_INDIRECT_ARGUMENT_DESC for which type.
I would find it helpful to have a table in the docs like this:
Thanks for looking into it!
The text was updated successfully, but these errors were encountered: