Sign in to follow this  

DX11 [DX11] Handling Multiple ResourceViews with Multislotted Resources

This topic is 2543 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'm trying to write a generic wrapper for DX11 shaders to abstract the code that will allow setting resources, samplers, constant buffers, etc. I was wondering how multiple resource views get handled when the resources themselves are multi-slotted and you make a single call to *SSetShaderResources(). For example, what happens when there's a call to *SSetShaderResources() for slot 0 and the underlying resource is an array of 4 2D textures? I presume this would fill up slots 0-3. The call for that would look like this:
p_Device->*SSetShaderResources(0, 1, &pMultiSlotRV);  //underlying resource is Texture2D[4] so it uses 4 slots

So then my question is, what if you had a resource view immediately after that resource? Obviously on the graphics hardware, you would want that placed in slot 4. With a separate call to *SSetShaderResources() the code would look like:
p_Device->*SSetShaderResources(4, 1, &NextRV);  //manually inserted after the previous resource (but requires knowledge of it's placement)

Successively called:

p_Device->*SSetShaderResources(0, 1, &pMultiSlotRV);
p_Device->*SSetShaderResources(4, 1, &NextRV);

The question is what happens if you want to set both resources in the same call to *SSetShaderResources(), or is that is even possible? Basically what would happen with this snippet of code:

ID3D11ShaderResourceView * twoRV[2];
twoRV[0] = pMultiSlotRV; //uses slots 0-3
twoRV[1] = NextRV; //uses slot 4
p_Device->*SSetShaderResources(0, 2, &twoRV);

It seems to me that the above code would get unrolled into two calls that look like this:

p_Device->*SSetShaderResources(0, 1, &pMultiSlotRV);
p_Device->*SSetShaderResources(1, 1, &NextRV);

So the that would cause the first resource to fill slots 0-3, but then the next resource view would overwrite whatever is in slot 1 which is supposed to be a part of the first resource that is multi-slotted. Can someone explain what the behavior is in the senario of making 1 call with both resource reviews in an an array? It would spare me a lot of time staring at a screen with garbage (given I'm still pretty newb). Thanks in advance!

Share this post

Link to post
Share on other sites
If you're using a texture array, then it takes just one slot and you access it in the shader as a Texture2DArray instead of a Texture2D. So when you sample it, you specify which texture in the array to use, in addition to the texture coordinate.

Share this post

Link to post
Share on other sites
My point confusion lies in the fact that I'm writing a lot of this code based on the reference documentation and am using ShaderReflection. The D3D11_SHADER_INPUT_BIND_DESC structure has BindPoint and BindCount members. Can you explain how those correlate to number of resource views and start slot that should be used to set the associated parameters?

I'm tinkering around with reflection, examining the output of it based on changing the structure of shaders, and it seems that explicit arrays are flattened into their separate components as used and occupy separate bind slots. I tested a Texture2DArray and that only occupies one too. So really, what is the difference between Texture2DArray and Texture2D[n]? I may be asking these questions far too early.

Share this post

Link to post
Share on other sites
The difference between Texture2DArray and Texture2D[n] is the the Texture2DArray is a single resource with multiple subresources referred to as texture slices. A Texture2D[n] is just an array of individual, independent resources.

The other thing to keep in mind is that a shader resource view is used to bind a resource to the pipeline. You can create a separate shader resource view over each subresource of a Texture2D or Texture2DArray, where a subresource can be from mip maps or texture slices (see the docs for details about what can be selected with a SRV). Therefore, if you declare in HLSL Texture2D[n], then you can create one shader resource view for each of the mip maps of a single Texture2D and bind them to 'n' SRV slots. In HLSL it will appear as an array of unrelated resources, but in C++ it is actually all the same resource.

You just need to get used to the difference between a shader resource view and the resources that stand behind them.

Share this post

Link to post
Share on other sites
I think I have a better understanding now. If I go back to my original issue, there really isn't one at all. What I called a multi-slot resource view, cannot really exist. If I create a 2D texture array programmatically, with only a single resource view, in HLSL it will still only take up 1 slot no matter how big the array is. Ideally that slot should populate Texure2DArray variable in HLSL correct? Also, if I force-fit a Texture2DArray into a Texture2D or Texture1D in HLSL, it would just be interpreted however it is being used which would likely be broken?

So every variable type declared in HLSL takes up only 1 resource-view/slot unless declared with array syntax. What is populated in that slot (a resource view) is just memory that will be interpreted when the HLSL uses variable.

Share this post

Link to post
Share on other sites
I'm not sure if the runtime will let you do that or not. At the very least, I would expect a warning when you actually execute the draw call that would use the texture.

When you create an SRV you specify the view dimension, which has distinct entries for Texture2D and Texture2DArray. I would suggest to try doing the cross setting and see what comes out of the debug output. This is often the only way to know for sure about edge cases like this, since they aren't directly specified in the documentation.

Share this post

Link to post
Share on other sites

This topic is 2543 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
    • Total Posts
  • 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(,; //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.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:
      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
      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
      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
    • By ADDMX
      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