# DX11 DX11 VSSetConstantBuffers - Send more than one array

This topic is 1820 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

## Recommended Posts

Hi guys,

right now I'm having a small problem, in the command from the device context called VSSetConstantBuffers, the parameters are as following:

void VSSetConstantBuffers(
[in]  UINT StartSlot,
[in]  UINT NumBuffers,
[in]  ID3D11Buffer *const *ppConstantBuffers
);


Now the number of buffers is easy when you have two arrays of constant buffers, but the ID3D11Buffer *const *ppConstantBuffers isn't so easy. My first approach was to combine the two arrays of ID3D11Buffer*(s), but that could become quite slow as this is called quite frequent. So is there a quick way to send two arrays of buffers, maybe call the function twice and change the startslot?

So how can i do this?

Thank You

##### Share on other sites

I think you already stated the best way to do the call - just make two calls to the function with a different start slot to put everything where you need them.  However, it would probably be best to try it out both ways to see what is more expensive.  Essentially you are trading a memcpy for an API call, and there are lots of variables that could help or hurt either method.  Most likely the difference between the two calls is not going to be noticeable, since the heavy costs are likely to be elsewhere in your frame.

You should also ensure that you are doing all of the optimizations you can, such as ensuring that any buffers that can be reused between calls are allowed to remain there, and to make sure you are using as few of buffers as you can.  I would be curious to hear if you detect any significant difference between the two methods.

##### Share on other sites

Here is some code that I used to bind multiple buffers at once...  Granted, your situation is a bit different with the constant buffer, but the syntax should be close.

TBH, I prefer to push one buffer at a time, (I set the constant buffer in one activity, then set the static vertexbuffer data, then set instance buffer data every frame or so).

HTH

/******************************************************************/
void ModelRenderer::BindInitialBuffer()
{

unsigned int offsets[2] = {0,0};
unsigned int strides[2];

ID3D11Buffer* bufferPointers[2];

strides[0] = sizeof(NS::Vertex);
strides[1] = sizeof(Position);

bufferPointers[0] = ModelRenderer::StaticBuffer.Get();
bufferPointers[1] = ModelRenderer::InstanceBuffer.Get();

DeviceManager::DeviceContext->IASetVertexBuffers(
0,                                 // First Input Slot for Binding
2,                                 // Number of Buffers
bufferPointers,                    // Buffer Pointer(s)
strides,                           // Stride(s)
offsets                            // Offset(s)
);

DeviceManager::DeviceContext->IASetInputLayout(ModelRenderer::InitialLayout.Get());
DeviceManager::DeviceContext->IASetPrimitiveTopology(D3D11_PRIMITIVE_TOPOLOGY_TRIANGLELIST);

}

Edited by e.s.

• 9
• 9
• 12
• 10
• 12
• ### Similar Content

• By kan123
Hello,
DX9Ex. I have the problem with driver stability in time of serial renderings, which i try to use for image processing in memory with fragment shaders. For big bitmaps the video driver sometimes becomes unstable ("Display driver stopped responding and has recovered") and, for instance, if the media player runs video in background, it sometimes freezes and distorts. I tried to use next methods of IDirect3DDevice9Ex:
WaitForVBlank(0);
EvictManagedResources();
with purpose to give some time for GPU between scenes, but it seems to be has not notable effect in this case. I don't want to reinitilialize subsystem for every step to avoid performance loss.

• I wanted to see how others are currently handling descriptor heap updates and management.
I've read a few articles and there tends to be three major strategies :
1 ) You split up descriptor heaps per shader stage ( i.e one for vertex shader , pixel , hull, etc)
2) You have one descriptor heap for an entire pipeline
3) You split up descriptor heaps for update each update frequency (i.e EResourceSet_PerInstance , EResourceSet_PerPass , EResourceSet_PerMaterial, etc)
The benefits of the first two approaches is that it makes it easier to port current code, and descriptor / resource descriptor management and updating tends to be easier to manage, but it seems to be not as efficient.
The benefits of the third approach seems to be that it's the most efficient because you only manage and update objects when they change.

• hi,
until now i use typical vertexshader approach for skinning with a Constantbuffer containing the transform matrix for the bones and an the vertexbuffer containing bone index and bone weight.
Now i have implemented realtime environment  probe cubemaping so i have to render my scene from many point of views and the time for skinning takes too long because it is recalculated for every side of the cubemap.
For Info i am working on Win7 an therefore use one Shadermodel 5.0 not 5.x that have more options, or is there a way to use 5.x in Win 7
My Graphic Card is Directx 12 compatible NVidia GTX 960
the member turanszkij has posted a good for me understandable compute shader. ( for Info: in his engine he uses an optimized version of it )
Now my questions
is it possible to feed the compute shader with my orignial vertexbuffer or do i have to copy it in several ByteAdressBuffers as implemented in the following code ?
the same question is about the constant buffer of the matrixes
my more urgent question is how do i feed my normal pipeline with the result of the compute Shader which are 2 RWByteAddressBuffers that contain position an normal
for example i could use 2 vertexbuffer bindings
1 containing only the uv coordinates
2.containing position and normal
How do i copy from the RWByteAddressBuffers to the vertexbuffer ?

(Code from turanszkij )
Here is my shader implementation for skinning a mesh in a compute shader:

• Hi, can someone please explain why this is giving an assertion EyePosition!=0 exception?

It looks like DirectX doesnt want the 2nd parameter to be a zero vector in the assertion, but I passed in a zero vector with this exact same code in another program and it ran just fine. (Here is the version of the code that worked - note XMLoadFloat3(&m_lookAt) parameter value is (0,0,0) at runtime - I debugged it - but it throws no exceptions.
and here is the repo with the alternative version of the code that is working with a value of (0,0,0) for the second parameter.

• Hi, can somebody please tell me in clear simple steps how to debug and step through an hlsl shader file?
I already did Debug > Start Graphics Debugging > then captured some frames from Visual Studio and
double clicked on the frame to open it, but no idea where to go from there.

I've been searching for hours and there's no information on this, not even on the Microsoft Website!
They say "open the  Graphics Pixel History window" but there is no such window!
Then they say, in the "Pipeline Stages choose Start Debugging"  but the Start Debugging option is nowhere to be found in the whole interface.
Also, how do I even open the hlsl file that I want to set a break point in from inside the Graphics Debugger?

All I want to do is set a break point in a specific hlsl file, step thru it, and see the data, but this is so unbelievably complicated