• Advertisement
Sign in to follow this  

DX11 i'm confusing with with dx11 shader

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

[font="Consolas"][font="Consolas"]
does all width of a register is 4 floats lang? how can a martix aligned with one register?


i thought a register is 128bit, matrix is 128bit x 4.
cbuffer cbChangeOnResize : register( b1 )

{

matrix Projection;

};

cbuffer cbNeverChanges : register( b0 )

{

matrix View;

};

[/font][/font]

Share this post


Link to post
Share on other sites
Advertisement

A float is 32 bits wide and 4x32 == 128, so you thought correctly.



but a Matrix could be 128*4 , am i right?
so how can you set a container which only can hold 4 floats to store a matrix which cap is 4X4 floats?

plz~ :)

Share this post


Link to post
Share on other sites
[float]\
[float] \ b
[float] / 0 <----- [font="Consolas"]matrix View 4[float]x4[float][/font]
[float]/
[float]\
[float] \ b
[float] / 1
[float]/
[float]\
[float] \ b
[float] / 2
[float]/


look the pic, if i use view to fill b0, obviously it even occupy not b0 and b1,b2, the space still not enough...

Share this post


Link to post
Share on other sites
I think you are confusing constant buffers with constant registers from the older API levels. A constant buffer holds a bunch of data, which can consist of some combination of floats, ints and bools (and structs of them as well). These data are used to fill 4 component vector registers.

Each complete constant buffer is bound to a single buffer slot with the ID3D11DeviceContext::xSSetConstantBuffers(...). These buffer slots are not the same as a register - they are only used to reference a complete constant buffer. So it can appear that each matrix is only taking up a single four component register when in reality it is taking up one constant buffer slot.

However, to the best of my knowledge the constant buffers are referenced with the cb0, cb1, ..., cb[n] syntax instead of just a "b[n]" syntax. I don't normally track the slots that each buffer uses, so I'm not 100% sure about that point though... It would probably be easy to check if you produce a code listing from your shader with the FXC.exe tool (which can be found in the SDK).

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 Karol Plewa
      Hi, 
       
      I am working on a project where I'm trying to use Forward Plus Rendering on point lights. I have a simple reflective scene with many point lights moving around it. I am using effects file (.fx) to keep my shaders in one place. I am having a problem with Compute Shader code. I cannot get it to work properly and calculate the tiles and lighting properly. 
       
      Is there anyone that is wishing to help me set up my compute shader?
      Thank you in advance for any replies and interest!
    • 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?
       
      .
  • Advertisement