• Advertisement
Sign in to follow this  

DX11 [DX11] Constant buffer layout

This topic is 2350 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

I use Shader reflection to get the layout of each constant buffer used by each shader and the variable types/descs contained in it. So when I load a shader I create an array of constant buffer layouts (each layout containing an array of variables info). Then when I want to apply a certain material to an object I have to iterate through the array of variables types/descs and the parameters contained in the material object and find matches in order to update the constant buffers... Like this:
[source]
struct ShaderVariable
{
D3D11_SHADER_VARIABLE_DESC desc;
D3D11_SHADER_TYPE_DESC typeDesc;
};

struct ConstantBufferLayout
{
D3D11_SHADER_BUFFER_DESC desc;
ShaderVariable* variables;
};

//[...]

UINT m_NumConstantBuffers;
ConstantBufferLayout* m_ConstantBufferLayouts;

//[...]

for(int i = 0; i < m_NumConstantBuffers; i++)
{
for(int j = 0; j < m_ConstantBufferLayouts.desc.Variables; i++)
{
for(int k = 0; k < material.m_NumParamenters; k++)
{
if(m_ConstantBufferLayouts.variables[j].Name == material.m_Paramenters[k].Name)
{
material.addParameterToCBuffer(i, material.m_Paramenters[k];
}
}
}
}
[/source]

However searching for matches like this isn't as fast as I would like, and I also have to find matches between material shader resources and the shader resources needed by each shader. So does anyone has an idea how to fast is faster? Maybe a way to handle the parameters and the constant buffers layouts without have to find matches in the names each frame...

Share this post


Link to post
Share on other sites
Advertisement
I just have 16 unnamed vectors for each shader and let the shaders use macro definitions to name them. Arg[0..15].xyzw
Some properties like color and transformation should just be static and named to make most shaders easy to use.

Share this post


Link to post
Share on other sites
Then when I want to apply a certain material to an object I have to iterate through the array of variables types/descs and the parameters contained in the material object and find matches in order to update the constant buffers...
Instead of storing two copies of the data, and you could just store the one copy -- i.e. instead of storing values in a 'material' and copying them into a cbuffer, just store them in the cbuffer to begin with.

Can you explain what your "material" type is?

Share this post


Link to post
Share on other sites

[quote name='TiagoCosta' timestamp='1315997663' post='4861490']Then when I want to apply a certain material to an object I have to iterate through the array of variables types/descs and the parameters contained in the material object and find matches in order to update the constant buffers...

Instead of storing two copies of the data, and you could just store the one copy -- i.e. instead of storing values in a 'material' and copying them into a cbuffer, just store them in the cbuffer to begin with.

Can you explain what your "material" type is?
[/quote]

The thing is that some values might change between frames, like world/view/projection matrix, camera position, and even some material-related values like diffuse color.

My "material" type is just a class containing an array of parameters (each parameter has a type (constant, texture), a name, and a value) and the shader ID used by the material

Share this post


Link to post
Share on other sites
Keep those all separate. Stuff like view matrix or projection matrices only change once per frame, so have those in a constant buffer with other per-frame constants. Make 1 HLSL definition for that constant buffer and #include it in your shaders, and then you won't have to reflect every shader to get the memory layout. If you want, you can do similar stuff with stuff that changed per-draw (like a world matrix). Material parameters that never change should be in one constant buffer that you make when you create the material, so that you only have to set the values once when you load it. Dynamic material parameters can go in another constant buffer, or perhaps in a buffer with other per-draw constants.

Share this post


Link to post
Share on other sites

Keep those all separate. Stuff like view matrix or projection matrices only change once per frame, so have those in a constant buffer with other per-frame constants. Make 1 HLSL definition for that constant buffer and #include it in your shaders, and then you won't have to reflect every shader to get the memory layout. If you want, you can do similar stuff with stuff that changed per-draw (like a world matrix). Material parameters that never change should be in one constant buffer that you make when you create the material, so that you only have to set the values once when you load it. Dynamic material parameters can go in another constant buffer, or perhaps in a buffer with other per-draw constants.


I have the constants sorted by update frequency in different constant buffers like you suggest.

However some shaders need view / projection / view-projection matrices and others might only need view matrix so I never know which matrices a shader might need.
Or could I register a constant buffer slot to hold a camera related data constant buffer and put all camera related data in it so every shader has access to it. :)

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By turanszkij
      Hi, right now building my engine in visual studio involves a shader compiling step to build hlsl 5.0 shaders. I have a separate project which only includes shader sources and the compiler is the visual studio integrated fxc compiler. I like this method because on any PC that has visual studio installed, I can just download the solution from GitHub and everything just builds without additional dependencies and using the latest version of the compiler. I also like it because the shaders are included in the solution explorer and easy to browse, and double-click to open (opening files can be really a pain in the ass in visual studio run in admin mode). Also it's nice that VS displays the build output/errors in the output window.
      But now I have the HLSL 6 compiler and want to build hlsl 6 shaders as well (and as I understand I can also compile vulkan compatible shaders with it later). Any idea how to do this nicely? I want only a single project containing shader sources, like it is now, but build them for different targets. I guess adding different building projects would be the way to go that reference the shader source project? But how would they differentiate from shader type of the sources (eg. pixel shader, compute shader,etc.)? Now the shader building project contains for each shader the shader type, how can other building projects reference that?
      Anyone with some experience in this?
    • By osiris_dev
      Hello!
      Have a problem with reflection shader for D3D11:
      1>engine_render_d3d11_system.obj : error LNK2001: unresolved external symbol IID_ID3D11ShaderReflection
      I tried to add this:
      #include <D3D11Shader.h>
      #include <D3Dcompiler.h>
      #include <D3DCompiler.inl>
      #pragma comment(lib, "D3DCompiler.lib")
      //#pragma comment(lib, "D3DCompiler_47.lib")
      As MSDN tells me but still no fortune. I think lot of people did that already, what I missing?
      I also find this article http://mattfife.com/?p=470
      where recommend to use SDK headers and libs before Wind SDK, but I am not using DirectX SDK for this project at all, should I?
    • By trojanfoe
      Hi there, this is my first post in what looks to be a very interesting forum.
      I am using DirectXTK to put together my 2D game engine but would like to use the GPU depth buffer in order to avoid sorting back-to-front on the CPU and I think I also want to use GPU instancing, so can I do that with SpriteBatch or am I looking at implementing my own sprite rendering?
      Thanks in advance!
    • By Matt_Aufderheide
      I am trying to draw a screen-aligned quad with arbitrary sizes.
       
      currently I just send 4 vertices to the vertex shader like so:
      pDevCon->IASetPrimitiveTopology(D3D_PRIMITIVE_TOPOLOGY_TRIANGLESTRIP);
      pDevCon->Draw(4, 0);
       
      then in the vertex shader I am doing this:
      float4 main(uint vI : SV_VERTEXID) : SV_POSITION
      {
       float2 texcoord = float2(vI & 1, vI >> 1);
      return float4((texcoord.x - 0.5f) * 2, -(texcoord.y - 0.5f) * 2, 0, 1);
      }
      that gets me a screen-sized quad...ok .. what's the correct way to get arbitrary sizes?...I have messed around with various numbers, but I think I don't quite get something in these relationships.
      one thing I tried is: 
       
      float4 quad = float4((texcoord.x - (xpos/screensizex)) * (width/screensizex), -(texcoord.y - (ypos/screensizey)) * (height/screensizey), 0, 1);
       
      .. where xpos and ypos is number of pixels from upper right corner..width and height is the desired size of the quad in pixels
      this gets me somewhat close, but not right.. a bit too small..so I'm missing something ..any ideas?
       
      .
    • By Stewie.G
      Hi,
      I've been trying to implement a gaussian blur recently, it would seem the best way to achieve this is by running a bur on one axis, then another blur on the other axis.
      I think I have successfully implemented the blur part per axis, but now I have to blend both calls with a proper BlendState, at least I think this is where my problem is.
      Here are my passes:
      RasterizerState DisableCulling { CullMode = BACK; }; BlendState AdditiveBlend { BlendEnable[0] = TRUE; BlendEnable[1] = TRUE; SrcBlend[0] = SRC_COLOR; BlendOp[0] = ADD; BlendOp[1] = ADD; SrcBlend[1] = SRC_COLOR; }; technique11 BlockTech { pass P0 { SetVertexShader(CompileShader(vs_5_0, VS())); SetGeometryShader(NULL); SetPixelShader(CompileShader(ps_5_0, PS_BlurV())); SetRasterizerState(DisableCulling); SetBlendState(AdditiveBlend, float4(0.0, 0.0, 0.0, 0.0), 0xffffffff); } pass P1 { SetVertexShader(CompileShader(vs_5_0, VS())); SetGeometryShader(NULL); SetPixelShader(CompileShader(ps_5_0, PS_BlurH())); SetRasterizerState(DisableCulling); } }  
      D3DX11_TECHNIQUE_DESC techDesc; mBlockEffect->mTech->GetDesc( &techDesc ); for(UINT p = 0; p < techDesc.Passes; ++p) { deviceContext->IASetVertexBuffers(0, 2, bufferPointers, stride, offset); deviceContext->IASetIndexBuffer(mIB, DXGI_FORMAT_R32_UINT, 0); mBlockEffect->mTech->GetPassByIndex(p)->Apply(0, deviceContext); deviceContext->DrawIndexedInstanced(36, mNumberOfActiveCubes, 0, 0, 0); } No blur

       
      PS_BlurV

      PS_BlurH

      P0 + P1

      As you can see, it does not work at all.
      I think the issue is in my BlendState, but I am not sure.
      I've seen many articles going with the render to texture approach, but I've also seen articles where both shaders were called in succession, and it worked just fine, I'd like to go with that second approach. Unfortunately, the code was in OpenGL where the syntax for running multiple passes is quite different (http://rastergrid.com/blog/2010/09/efficient-gaussian-blur-with-linear-sampling/). So I need some help doing the same in HLSL :-)
       
      Thanks!
  • Advertisement