• Advertisement
Sign in to follow this  

DX11 Vertex shader to pixel shader - way of sharing info?

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

Hello everyone,

 

I am using DX9 and having trouble trying to optimize some SM 3.0 shaders, the thing is that I have all the passable through data between vertex shader and pixel shader full and I dont know how to do it in order to get all the operations only needed in the pixel shader be done just there...in the pixel shader wacko.png .

 

If it were a kind of instruction like SetStreamSource but directly for the pixel shader only to pass there too the same info like passed before to the vertex shader or any other way of reusing in the pixel shader the same info streamed into the vertex shader before like skining info or even instancing info without requiring the valuable few slots that DX9 have?.

 

So reached to this point and after wasting nice times, I think I need some ideas about, please be different of "Pass all to DX11" because atm this isnt a possible option hahaha.

 

Thanks in advance.

Share this post


Link to post
Share on other sites
Advertisement

Haha, well indeed I knew that since the beginning. I am asking if is there any way to share as a pre declaration variables those which can be used both for the pixel and vertex shader without having to pass that data through the tiny COLOR(n) TEXCOORDS(n) pipe which in DX9 is two for the color and eight for the texcoords.

 

This should be done for saving many calculations done in the vertex shader for the pixel shader and so...

Share this post


Link to post
Share on other sites

There are many things for which I want to make for, one is that I have a motion blur effect implemented which needs the actual and last screen position, I use skinning and instancing so the current world matrix must be calculated on the vertex shader, but the lastPosition should be in the pixel shader.

 

So to calculate that old world matrix there the skinning and instancing info must be passed via which seems the only way to do, COLOR(n) TEXCOORDS(n).

 

For me it seems a real waste of precious passing slots, and my answer is, is there any other way to do?

 

Thank you.

Share this post


Link to post
Share on other sites

The slots are there for communication from vertex shader to pixel shader: that's the way you pass info between them.

 

You need to get this "waste" mentality out of your head.  It's not a "waste" if you're using them for a purpose.  You need to pass the info, the slots are for passing the info, so just use (not "waste", "use") the slots.

Share this post


Link to post
Share on other sites


So to calculate that old world matrix there the skinning and instancing info must be passed via which seems the only way to do, COLOR(n) TEXCOORDS(n).

 

Can't you just pass the result of that (i.e. the "lastPosition") to the pixel shader? That's a lot less data than the matrix, skinning info, etc...

 


For me it seems a real waste of precious passing slots, and my answer is, is there any other way to do?

 

Well the other way to get data into a pixel shader is via the textures :-). So, thinking outside the box here, you can put the data you need in a texture. Obviously this data can't come from the vertex shader, it must have been written to in a previous draw call. But your vertex shader could possibly pass a texture coordinate to the pixel shader that tells it which part of the texture to sample from to get more data. That's a pretty complicated proposition though.

Share this post


Link to post
Share on other sites

The slots are there for communication from vertex shader to pixel shader: that's the way you pass info between them.

 

You need to get this "waste" mentality out of your head.  It's not a "waste" if you're using them for a purpose.  You need to pass the info, the slots are for passing the info, so just use (not "waste", "use") the slots.

 

Re: I will try it out, the thing is there should be a  way of having a vertex stream linked data as for the vertex shader is, for the pixel shader also too, it should be shared memory at the same cost because it is just the same info. Thank you.

 

Can't you just pass the result of that (i.e. the "lastPosition") to the pixel shader? That's a lot less data than the matrix, skinning info, etc...

 

Re: Yes, thats what I am doing right now, but there are many faces to be culled that will :

1. Adquire the last world matrix by skinning+instancing

2. Adquire then the worldviewmatrix to adquire the last position.

 

Well the other way to get data into a pixel shader is via the textures :-). So, thinking outside the box here, you can put the data you need in a texture. Obviously this data can't come from the vertex shader, it must have been written to in a previous draw call. But your vertex shader could possibly pass a texture coordinate to the pixel shader that tells it which part of the texture to sample from to get more data. That's a pretty complicated proposition though.

 

Re: That is the only solution I reached to the skinning is done by textures so i will try passing the indexes to the pixel shader, I referred to that as a  waste because I dont understand why it cant be just streamed in as I did with the vertex shader as BLENDINDICES+BLENDWEIGHT... isnt really possible?

 

I thank you so much for all the people who answered this post, I am at the same point now, but at least I dont feel so that alone rolleyes.gif .

Share this post


Link to post
Share on other sites
The problem you are running into is simply because of the details of DX9 era hardware; the vertex and pixel shaders tended to be implemented in different silicon with different abilities and above all different interconnects to memory. For the longest time DX9 hardware didn't have a connection between the vertex shaders and the hardware for texture sampling, for example.

In this case the pixel shaders have access to three sources of information;
- textures
- data from previous vertex shader stages
- constant data "in registers"

Those are your 'data in paths' and only paths.

The only way to get a more complex memory subsystem is to break from hardware with those limits which means breaking from the API; D3D11 and OpenGL4.x allow you to attach many more streams of input data to the various shader stages (and indeed, output too with 11.1 allowing output buffers on all stages and OpenGL4.x having the same functionality).

Share this post


Link to post
Share on other sites

Thank you for that history appointment phantom, at least for me has been quite enlightening.

 

Also I would like to ask for forgiveness about if my english could inflict any eyes bleeding.

 

I will try to continue the way with this DX9 knowing this "era" was still quite dark between the relation of graphics pipeline programmers and hardware producers hahaha.

 

Welcome to the new DX11 era, I will want to get there fast :), maybe the jump to there from DX9 obviating DX10 will worth?. I am still supporting DX9 because of compatibility issues only.

Share this post


Link to post
Share on other sites
Avoiding DX10 is the best plan; DX11 works on the same hardware (via feature levels to expose what the hardware can do) and is a better API in general - there is no need to worry about the existence of DX10 at this point smile.png

Share this post


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

  • Advertisement
  • Advertisement
  • Popular Now

  • Advertisement
  • Similar Content

    • By AxeGuywithanAxe
      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.
    • By evelyn4you
      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 )
      https://turanszkij.wordpress.com/2017/09/09/skinning-in-compute-shader/
      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:
      1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 struct Bone { float4x4 pose; }; StructuredBuffer<Bone> boneBuffer;   ByteAddressBuffer vertexBuffer_POS; // T-Pose pos ByteAddressBuffer vertexBuffer_NOR; // T-Pose normal ByteAddressBuffer vertexBuffer_WEI; // bone weights ByteAddressBuffer vertexBuffer_BON; // bone indices   RWByteAddressBuffer streamoutBuffer_POS; // skinned pos RWByteAddressBuffer streamoutBuffer_NOR; // skinned normal RWByteAddressBuffer streamoutBuffer_PRE; // previous frame skinned pos   inline void Skinning(inout float4 pos, inout float4 nor, in float4 inBon, in float4 inWei) {  float4 p = 0, pp = 0;  float3 n = 0;  float4x4 m;  float3x3 m3;  float weisum = 0;   // force loop to reduce register pressure  // though this way we can not interleave TEX - ALU operations  [loop]  for (uint i = 0; ((i &lt; 4) &amp;&amp; (weisum&lt;1.0f)); ++i)  {  m = boneBuffer[(uint)inBon].pose;  m3 = (float3x3)m;   p += mul(float4(pos.xyz, 1), m)*inWei;  n += mul(nor.xyz, m3)*inWei;   weisum += inWei;  }   bool w = any(inWei);  pos.xyz = w ? p.xyz : pos.xyz;  nor.xyz = w ? n : nor.xyz; }   [numthreads(1024, 1, 1)] void main( uint3 DTid : SV_DispatchThreadID ) {  const uint fetchAddress = DTid.x * 16; // stride is 16 bytes for each vertex buffer now...   uint4 pos_u = vertexBuffer_POS.Load4(fetchAddress);  uint4 nor_u = vertexBuffer_NOR.Load4(fetchAddress);  uint4 wei_u = vertexBuffer_WEI.Load4(fetchAddress);  uint4 bon_u = vertexBuffer_BON.Load4(fetchAddress);   float4 pos = asfloat(pos_u);  float4 nor = asfloat(nor_u);  float4 wei = asfloat(wei_u);  float4 bon = asfloat(bon_u);   Skinning(pos, nor, bon, wei);   pos_u = asuint(pos);  nor_u = asuint(nor);   // copy prev frame current pos to current frame prev pos streamoutBuffer_PRE.Store4(fetchAddress, streamoutBuffer_POS.Load4(fetchAddress)); // write out skinned props:  streamoutBuffer_POS.Store4(fetchAddress, pos_u);  streamoutBuffer_NOR.Store4(fetchAddress, nor_u); }  
    • By mister345
      Hi, can someone please explain why this is giving an assertion EyePosition!=0 exception?
       
      _lightBufferVS->viewMatrix = DirectX::XMMatrixLookAtLH(XMLoadFloat3(&_lightBufferVS->position), XMLoadFloat3(&_lookAt), XMLoadFloat3(&up));
      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.
          m_viewMatrix = DirectX::XMMatrixLookAtLH(XMLoadFloat3(&m_position), XMLoadFloat3(&m_lookAt), XMLoadFloat3(&up)); Here is the repo for the broken code (See LightClass) https://github.com/mister51213/DirectX11Engine/blob/master/DirectX11Engine/LightClass.cpp
      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.
      https://github.com/mister51213/DX11Port_SoftShadows/blob/master/Engine/lightclass.cpp
    • By mister345
      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
      and Microsoft's instructions are horrible! Somebody please, please help.
       
       
       

    • By mister345
      I finally ported Rastertek's tutorial # 42 on soft shadows and blur shading. This tutorial has a ton of really useful effects and there's no working version anywhere online.
      Unfortunately it just draws a black screen. Not sure what's causing it. I'm guessing the camera or ortho matrix transforms are wrong, light directions, or maybe texture resources not being properly initialized.  I didnt change any of the variables though, only upgraded all types and functions DirectX3DVector3 to XMFLOAT3, and used DirectXTK for texture loading. If anyone is willing to take a look at what might be causing the black screen, maybe something pops out to you, let me know, thanks.
      https://github.com/mister51213/DX11Port_SoftShadows
       
      Also, for reference, here's tutorial #40 which has normal shadows but no blur, which I also ported, and it works perfectly.
      https://github.com/mister51213/DX11Port_ShadowMapping
       
  • Advertisement