• Advertisement
Sign in to follow this  

DX11 [D3D11] Creating a dynamic texture?

This topic is 2674 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've been trying to figure out how to create a blank texture that I can fill with information that I would generate every frame.

I'm using DirectX11 and I guess I'm looking for something like the old DirectX 9 function D3DXCreateTexture... wich allowed you to create a blank texture and then lock it to be loaded with the desired information.

I've found D3DX11CreateTextureFromFile, D3DX11CreateTextureFromMemory, and D3DX11CreateTextureFromResource, but I don't think any of those are what I'm looking for since according to MSDN the first takes a pointer to a file, the second a pointer to a file stored in memory, and the third a handle to a resource (whatever that is).

I would store the information to be loaded into the texture in an array such as Texture[width][height]...

How do I create a texture that I can update every frame with information stored in memory? I guess another way to ask my question would be, how do I create a texture I can update with procedurally generated colour information?

Share this post


Link to post
Share on other sites
Advertisement
You can use the CreateTexture2D Method of your device to create a texture, and then the UpdateSubresource Method of a device-context to update the texture data.

There is also a Map method for the device-context that can be used to give you a pointer to the texture-memory. If you want to use that method to update your texture, you need to create it with the appropriate CPU access flags and dynamic usage. See the D3D11_TEXTURE2D_DESC Structure for information on all the flags. UpdateSubresource will probably be more efficient.

Share this post


Link to post
Share on other sites
I would say DXGI_FORMAT_R8G8B8A8_UNORM, if you want the texture to contain a normal image. That's a 32-bit format with 8 bits for each channel, which is the common display mode.

Share this post


Link to post
Share on other sites
Thank you.

The following code shows where I'm at now. I've created a 2d texture, pointed at by pTexture, and now I'm trying to map values for each pixel:

D3D11_MAPPED_SUBRESOURCE texmap;
pImmediateContext->Map(pTexture, 0, D3D11_MAP_WRITE_DISCARD, 0, &texmap);
for (UINT i = 0; i < Width; i++)
{
for (UINT j = 0; j < Height; j++)
{
//What code goes here to set the colour value for each pixel?
}
}
pImmediateContext->Unmap(pTexture, 0);




How do I set the colour value for each pixel?

Share this post


Link to post
Share on other sites
The member void* D3D11_MAPPED_SUBRESOURCE::pData points to the block of memory. Cast this to a BYTE* which will let you go through the data as bytes. In this way, every 4 bytes stand for a single RGBA vector. Write in the color data as you see fit.

Share this post


Link to post
Share on other sites
Thank you.

I've decided to also try UpdateSubresource.

This is the code so far:


for(UINT i=0; i<Width*Height(); i++)
{
UINT32 Colour = 0xFFFFFFFF;
pImmediateContext()->UpdateSubresource(pTexture2D(), 0, (D3D11_BOX *)(pTexture2D() + i), &Colour, /*??*/, /*??*/);
}



Assuming I've treated the other parameters correctly I'm confused as to what to input for the last two parameters, being UINT SrcRowPitch and UINT SrcDepthPitch respectively.

For UINT SrCRowPitch is it the width of the texture or the width of the texture multiplied by the sixe of a texel? For SrcRowPitch is it 0 (given that is 2D) or is it 1 (being 1 texel deep), or is it the size of a texel?

Share this post


Link to post
Share on other sites
Well, I tried UINT SrcRowPitch = 0, and UINT SrcDepthPitch = 0, (because I did that in another part of my code when I updated a constant buffer in my shader file with updatesubresource), and the code fills the texture with white as desired BUT, after a while of running the program I get tons of exceptions with the error messages:

D3D11: ERROR: ID3D11DeviceContext::UpdateSubresource: pDstBox is not a valid box, as the End coordinates must be greater than or equal to the Start. *pDstBox = { {1653043880,8880072, 8881048}, {8880256, 8880340,8881064} }. [ RESOURCE_MANIPULATION ERROR #288: UPDATESUBRESOURCE_INVALIDDESTINATIONBOX ]
D3D11: Removing Device.
D3D11: ERROR: ID3D11DeviceContext::UpdateSubresource: pDstBox is not a valid box for the destination subresource. *pDstBox = { {8880072,8881048, 8880256}, {8880340, 8881064,1144210505} }. DstSubresource = { {0,0, 0}, {1600, 900,1} }. [ RESOURCE_MANIPULATION ERROR #288: UPDATESUBRESOURCE_INVALIDDESTINATIONBOX ]
D3D11: ERROR: ID3D11DeviceContext::UpdateSubresource: pDstBox is not a valid box for the destination subresource. *pDstBox = { {8881048,8880256, 8880340}, {8881064, 1144210505,1700016433} }. DstSubresource = { {0,0, 0}, {1600, 900,1} }. [ RESOURCE_MANIPULATION ERROR #288: UPDATESUBRESOURCE_INVALIDDESTINATIONBOX ]
D3D11: ERROR: ID3D11DeviceContext::UpdateSubresource: pDstBox is not a valid box for the destination subresource. *pDstBox = { {8880256,8880340, 8881064}, {1144210505, 1700016433,1920300152} }. DstSubresource = { {0,0, 0}, {1600, 900,1} }. [ RESOURCE_MANIPULATION ERROR #288: UPDATESUBRESOURCE_INVALIDDESTINATIONBOX ]
D3D11: ERROR: ID3D11DeviceContext::UpdateSubresource: pDstBox is not a valid box, as the End coordinates must be greater than or equal to the Start. *pDstBox = { {8880340,8881064, 1144210505}, {1700016433, 1920300152,4469349} }. [ RESOURCE_MANIPULATION ERROR #288: UPDATESUBRESOURCE_INVALIDDESTINATIONBOX ]
D3D11: ERROR: ID3D11DeviceContext::UpdateSubresource: pDstBox is not a valid box, as the End coordinates must be greater than or equal to the Start. *pDstBox = { {8881064,1144210505, 1700016433}, {1920300152, 4469349,3131961357} }. [ RESOURCE_MANIPULATION ERROR #288: UPDATESUBRESOURCE_INVALIDDESTINATIONBOX ]
D3D11: ERROR: ID3D11DeviceContext::UpdateSubresource: pDstBox is not a valid box, as the End coordinates must be greater than or equal to the Start. *pDstBox = { {1144210505,1700016433, 1920300152}, {4469349, 3131961357,3131961357} }. [ RESOURCE_MANIPULATION ERROR #288: UPDATESUBRESOURCE_INVALIDDESTINATIONBOX ]


These errors are repeated many many times.

How can I fix that?

Share this post


Link to post
Share on other sites
The documentation for UpdateSubresource explains how to use the destination box and source pitch. If you want to update your entire texture, you can specify NULL for the destination box.
SrcRowPitch is the distance in bytes from the start of one row of pixels to the start of the next, in the source data that is to be copied to the texture. Depth-pitch is only used for 3D textures. For constant-buffers or 1D-textures the row-pitch is also unused, since there is only one row.

Also, you don't need to loop over your texture and call UpdateSubresource multiple times, as one call can update the entire texture.

I would recommend doing it something like this:

desc.Format = DXGI_FORMAT_R8G8B8A8_UNORM;
desc.Usage = D3D11_USAGE_DEFAULT;
// dont need any CPU flags for UpdateSubresource
CreateTexture2D(...);

UINT32 *textureData = new UINT32[width * height];
textureData[0] = pixel 1;
textureData[1] = pixel 2;
...

// Note width*4 as each pixel is 4 bytes
pContext->UpdateSubresource(pTexture, 0, NULL, textureData, width*4, 0);


You can use the destination box if you only want to update part of the texture.

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