Sign in to follow this  

DX11 Directx11 - Shader Constantbuffers vs the world.

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

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hey!

i working on some dx11 stuff and are at the point where i need to be able to set shader variables easy and fast, since it gonna happen in runtime i am looking for the fastest way to do this.

At the moment i am struggeling with Constant buffers and i havent realy found another way to set shader input variabels, so my big question is :

How do i in the fastest CPU SPEED way set shadervariables? i need them to change on the fly for each frame.

Is CBuffers the way to do it?
Is there any other way to do it?
Is that otherway faster than remapping the cbuffer?

Would be glad for articels, information, tutorials and more!

cheers !

Share this post


Link to post
Share on other sites
If you want performance, than constant buffers are absolutely the way to go. No question. You obviously want to limit the amount of data that you map and update, and the way to do that is to group your constants based on how often they change. So for example if your view * projection matrix never changes the entire frame, put in a PerFrames cb and only set them once a frame. If you set a world matrix for each draw call, put that in a PerDraws cb.

Share this post


Link to post
Share on other sites
is PreFrame cb a different constant buffer than a regular Cbuffer?
is PreDraw cb a different constant buffer than a regular Cbuffer?

How do they work? (if they exsist?)

or do you just mean to have different cb in the shader with less data than a full global one?

Share this post


Link to post
Share on other sites
That does actually touch on something I've been wanting to ask about MJP. Say you want to set a VP matrix on a per frame basis. How would you go about that in detail.

In my framework I'm working without the DX effects as I wanted to learn the nitty gritty details. And when I reflect my shaders to find the bind information a given CB containing the VP matrix (for the sake of this example let it contain only that) it might give me different bind points for different shaders.

How exactly would I avoid having to bind the information for each shader. Even when specifying the CB register that doesn't change the bind points, and I just haven't been able to find any information regarding them.

Share this post


Link to post
Share on other sites
If you manually bind a constant buffer to a register using "register : (cb0)", then you can use that index to bind the D3D11 constant buffer at runtime. If you want you can keep your commonly-used constant buffers in a header file and #include that in all of your shaders, which makes it easier to manage.

Share this post


Link to post
Share on other sites
Another way to improve performance for CPU related configuration of the pipeline is to use the multithreading capabilities of D3D11. If you are using 2 or 4 cores to submit the requested changes into command lists, and then submit the command lists to the immediate context then you will almost surely be faster than doing it in a single thread on a single core.

Share this post


Link to post
Share on other sites
Ah, i see.
Than this brings me to another question.

Say i have 3 sets of CBs,
When i set thees and do the call "SetVSConstantBuffer" for the second one for example, should i set the "numBuff" to 1? or 2?

or is this where the register thing come into play?

Can some one give me a example & explenation of the cb & registery system?

i have understood it like this :

ConstantBuffer WorldViewProjection {
matrix World : World <--- in my c++ buffer i have to have a variable named that name?
};

Or is this wrong?

Cheers!

Share this post


Link to post
Share on other sites
Hey Tordin - Sorry for hijacking your thread like that.

As far as I can tell what you're doing is wrong. A constant buffer is a buffer like any other. It's a structure containing some data you would like your shader instance to use. In DX9-era shaders you would have a shader just declare the variables it would need - But in DX10/11 they switched to batching variables to the GPU to avoid the driver overhead caused by repeated updating of variables. Enter the constant buffer. It's a way to group up variables (be it matricies, floats, arrays whatever) based on usage.

An excample of a constant buffer declaration in a shader could be:

cbuffer CBObject : register(cb0) <-- The register here would be the slot you need to set.
{
float4x4 m_kWorldView;
float4x4 m_kWorldViewIT;
float4x4 m_kWorldViewProjection;
}

Hope this helped.

Share this post


Link to post
Share on other sites
So if i have three buffers

i would define them like this : ?

cbuffer CBObject : register(cb0)
{
float4x4 m_kWorldView;
float4x4 m_kWorldViewIT;
float4x4 m_kWorldViewProjection;
}

cbuffer CBObject : register(cb1)
{
float4x4 m_kWorldView;
float4x4 m_kWorldViewIT;
float4x4 m_kWorldViewProjection;
}

cbuffer CBObject : register(cb2)
{
float4x4 m_kWorldView;
float4x4 m_kWorldViewIT;
float4x4 m_kWorldViewProjection;
}


if i call the SetVsConstantbuffer(1,....);

i would assign stuff to the second buffer? not the first or the third one?
just because i sat the registery(cb1) there? is this correct?

Share this post


Link to post
Share on other sites
The VSSetConstantBuffers works like this: you specify which slot you want to start at, and how many constant buffers you want to set contiguously starting from the slot you specified. So if you pass 1 as StartSlot and then pass an array of 3 constant buffers, you will set those three constant buffers to slots 1, 2, and 3 respectively. If you want to just set one constant buffer, then you pass the slot you want to set it to and pass 1 for NumBuffers.

That said, that example you just outlined with three identical constant buffers declared will not compile. This is because you can't have multiple buffers with the same name declared in the same file, and you can't have the same parameter name declared in multiple constant buffers.

Share this post


Link to post
Share on other sites
Yes of corse that wont compile, that wasent the point eiter, the point was that i had understood it and hadent the time to write a correct shader!

Anyhow, to bring the subject up again, I have this shader :

cbuffer perFrame : register(cb0)
{
float3 floatP1;
float3 floatP2;
float3 floatP3;
float3 floatP4;
};

struct VSOUT
{
float4 pos : SV_POSITION;
float2 uv : TEXCOORD0;
};


Texture2D diffuse;
SamplerState samLin;


float4 mainPS(VSOUT inPS) : SV_Target
{
float4 color = diffuse.Sample(samLin,inPS.uv);
return color*floatP2.x;
}



And i try to set a row of 4 3d vectors, the first vector floatP1 gets it information, but the rest dosent!

and this is how i set the buffer! if you see ways to improve this, please tell me!


bool D3D11Device::SetPixelShaderVariableConstantBuffer(MORN_VARIABLE_BUFFER_PERFRAME data)
{
HRESULT hr;
D3D11_BUFFER_DESC cbDesc;
D3D11_SUBRESOURCE_DATA cbSubData;
D3D11_MAPPED_SUBRESOURCE cbMapped;
MORN_VARIABLE_BUFFER_PERFRAME* Buffer;

if(m_pPixelShaderCBuffer == NULL)
{
Buffer = &data;

ZeroMemory(&cbDesc,sizeof(cbDesc));
ZeroMemory(&cbSubData,sizeof(cbSubData));

cbDesc.ByteWidth = sizeof(MORN_VARIABLE_BUFFER_PERFRAME);
cbDesc.Usage = D3D11_USAGE_DYNAMIC;
cbDesc.BindFlags = D3D11_BIND_CONSTANT_BUFFER;
cbDesc.CPUAccessFlags = D3D11_CPU_ACCESS_WRITE;
cbDesc.MiscFlags = 0;
cbDesc.StructureByteStride = 0;

cbSubData.pSysMem = Buffer;
cbSubData.SysMemPitch = 0;
cbSubData.SysMemSlicePitch = 0;

int size = sizeof(MORN_VARIABLE_BUFFER_PERFRAME);

hr = m_pD3DDevice->CreateBuffer( &cbDesc, &cbSubData,
&m_pPixelShaderCBuffer );
if(ChekReturnError(hr))
return false;

m_pD3DContex->PSSetConstantBuffers( 0, 1, &m_pPixelShaderCBuffer );
return true;
}
else if(m_pPixelShaderCBuffer != NULL)
{
hr = m_pD3DContex->Map(m_pPixelShaderCBuffer,0,D3D11_MAP_WRITE_DISCARD,0,&cbMapped);
if(ChekReturnError(hr))
return false;

Buffer = (MORN_VARIABLE_BUFFER_PERFRAME*)cbMapped.pData;
for(int i = 0; i<4; ++i)
Buffer->fff[i] = data.fff[i];

m_pD3DContex->Unmap(m_pPixelShaderCBuffer,0);
m_pD3DContex->PSSetConstantBuffers( 0, 1, &m_pPixelShaderCBuffer );

return true;
}
}



So when i try to get information from the second 3d vector in the array, it´s pichblack!

Share this post


Link to post
Share on other sites
In constant buffers, float3's will be aligned to 16-byte boundaries due to the fact that registers are 16 bytes in size. So on the CPU side you need to either mirror that alignment using pragmas, or put in appropriate padding. See this for a full set of packing rules.

[Edited by - MJP on November 25, 2010 1:34:25 PM]

Share this post


Link to post
Share on other sites

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

If you intended to correct an error in the post then please contact us.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Forum Statistics

    • Total Topics
      628740
    • Total Posts
      2984470
  • Similar Content

    • By GreenGodDiary
      Having some issues with a geometry shader in a very basic DX app.
      We have an assignment where we are supposed to render a rotating textured quad, and in the geometry shader duplicate this quad and offset it by its normal. Very basic stuff essentially.
      My issue is that the duplicated quad, when rendered in front of the original quad, seems to fail the Z test and thus the original quad is rendered on top of it.
      Whats even weirder is that this only happens for one of the triangles in the duplicated quad, against one of the original quads triangles.

      Here's a video to show you what happens: Video (ignore the stretched textures)

      Here's my GS: (VS is simple passthrough shader and PS is just as basic)
      struct VS_OUT { float4 Pos : SV_POSITION; float2 UV : TEXCOORD; }; struct VS_IN { float4 Pos : POSITION; float2 UV : TEXCOORD; }; cbuffer cbPerObject : register(b0) { float4x4 WVP; }; [maxvertexcount(6)] void main( triangle VS_IN input[3], inout TriangleStream< VS_OUT > output ) { //Calculate normal float4 faceEdgeA = input[1].Pos - input[0].Pos; float4 faceEdgeB = input[2].Pos - input[0].Pos; float3 faceNormal = normalize(cross(faceEdgeA.xyz, faceEdgeB.xyz)); //Input triangle, transformed for (uint i = 0; i < 3; i++) { VS_OUT element; VS_IN vert = input[i]; element.Pos = mul(vert.Pos, WVP); element.UV = vert.UV; output.Append(element); } output.RestartStrip(); for (uint j = 0; j < 3; j++) { VS_OUT element; VS_IN vert = input[j]; element.Pos = mul(vert.Pos + float4(faceNormal, 0.0f), WVP); element.Pos.xyz; element.UV = vert.UV; output.Append(element); } }  
      I havent used geometry shaders much so im not 100% on what happens behind the scenes.
      Any tips appreciated! 
    • By mister345
      Hi, I'm building a game engine using DirectX11 in c++.
      I need a basic physics engine to handle collisions and motion, and no time to write my own.
      What is the easiest solution for this? Bullet and PhysX both seem too complicated and would still require writing my own wrapper classes, it seems. 
      I found this thing called PAL - physics abstraction layer that can support bullet, physx, etc, but it's so old and no info on how to download or install it.
      The simpler the better. Please let me know, thanks!
    • By Hexaa
      I try to draw lines with different thicknesses using the geometry shader approach from here:
      https://forum.libcinder.org/topic/smooth-thick-lines-using-geometry-shader
      It seems to work great on my development machine (some Intel HD). However, if I try it on my target (Nvidia NVS 300, yes it's old) I get different results. See the attached images. There
      seem to be gaps in my sine signal that the NVS 300 device creates, the intel does what I want and expect in the other picture.
      It's a shame, because I just can't figure out why. I expect it to be the same. I get no Error in the debug output, with enabled native debugging. I disabled culling with CullMode.None. Could it be some z-fighting? I have little clue about it but I tested to play around with the RasterizerStateDescription and DepthBias properties with no success, no change at all. Maybe I miss something there?
      I develop the application with SharpDX btw.
      Any clues or help is very welcome
       


    • By Beny Benz
      Hi,
      I'm currently trying to write a shader which shoud compute a fast fourier transform of some data, manipulating the transformed data, do an inverse FFT an then displaying the result as vertex offset and color. I use Unity3d and HLSL as shader language. One of the main problems is that the data should not be passed from CPU to GPU for every frame if possible. My original plan was to use a vertex shader and do the fft there, but I fail to find out how to store changing data betwen shader calls/passes. I found a technique called ping-ponging which seems to be based on writing and exchangeing render targets, but I couldn't find an example for HLSL as a vertex shader yet.
      I found https://social.msdn.microsoft.com/Forums/en-US/c79a3701-d028-41d9-ad74-a2b3b3958383/how-to-render-to-multiple-render-targets-in-hlsl?forum=xnaframework
      which seem to use COLOR0 and COLOR1 as such render targets.
      Is it even possible to do such calculations on the gpu only? (/in this shader stage?, because I need the result of the calculation to modify the vertex offsets there)
      I also saw the use of compute shaders in simmilar projects (ocean wave simulation), do they realy copy data between CPU / GPU for every frame?
      How does this ping-ponging / rendertarget switching technique work in HLSL?
      Have you seen an example of usage?
      Any answer would be helpfull.
      Thank you
      appswert
    • By ADDMX
      Hi
      Just a simple question about compute shaders (CS5, DX11).
      Do the atomic operations (InterlockedAdd in my case) should work without any issues on RWByteAddressBuffer and be globaly coherent ?
      I'v come back from CUDA world and commited fairly simple kernel that does some job, the pseudo-code is as follows:
      (both kernels use that same RWByteAddressBuffer)
      first kernel does some job and sets Result[0] = 0;
      (using Result.Store(0, 0))
      I'v checked with debugger, and indeed the value stored at dword 0 is 0
      now my second kernel
      RWByteAddressBuffer Result;  [numthreads(8, 8, 8)] void main() {     for (int i = 0; i < 5; i++)     {         uint4 v0 = DoSomeCalculations1();         uint4 v1 = DoSomeCalculations2();         uint4 v2 = DoSomeCalculations3();                  if (v0.w == 0 && v1.w == 0 && v2.w)             continue;         //    increment counter by 3, and get it previous value         // this should basically allocate space for 3 uint4 values in buffer         uint prev;         Result.InterlockedAdd(0, 3, prev);                  // this fills the buffer with 3 uint4 values (+1 is here as the first 16 bytes is occupied by DrawInstancedIndirect data)         Result.Store4((prev+0+1)*16, v0);         Result.Store4((prev+1+1)*16, v1);         Result.Store4((prev+2+1)*16, v2);     } } Now I invoke it with Dispatch(4,4,4)
      Now I use DrawInstancedIndirect to draw the buffer, but ocassionaly there is missed triangle here and there for a frame, as if the atomic counter does not work as expected
      do I need any additional synchronization there ?
      I'v tried 'AllMemoryBarrierWithGroupSync' at the end of kernel, but without effect.
      If I do not use atomic counter, and istead just output empty vertices (that will transform into degenerated triangles) the all is OK - as if I'm missing some form of synchronization, but I do not see such a thing in DX11.
      I'v tested on both old and new nvidia hardware (680M and 1080, the behaviour is that same).
       
  • Popular Now