• Advertisement
Sign in to follow this  

DX11 DX11 - Multiple Render Targets

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

Hi guys, again...

 

I'm having a problem with multiple render targets, where only the first render target gets filled out (has a value).

 

Setting the render targets:

DeferredRender.ApplyShader(dev, devcon);

DeferredRender.mDepth.ClearRenderTarget(devcon, zbuffer, 0, 0, 0, 1);
DeferredRender.mNormals.ClearRenderTarget(devcon, zbuffer, 0, 0, 0, 1);
DeferredRender.mLighting.ClearRenderTarget(devcon, zbuffer, 0, 0, 0, 1);

ID3D11RenderTargetView *deferredViews[3];

deferredViews[0] = DeferredRender.mDepth.m_renderTargetView;
deferredViews[1] = DeferredRender.mNormals.m_renderTargetView;
deferredViews[2] = DeferredRender.mLighting.m_renderTargetView;

devcon->OMSetRenderTargets(3, deferredViews, zbuffer);

RenderScene(STATE_DEFERRED);

gBuffer_Depth = DeferredRender.mDepth.GetShaderResourceView();
gBuffer_Normals = DeferredRender.mNormals.GetShaderResourceView();
gBuffer_Lighting = DeferredRender.mLighting.GetShaderResourceView();

Pixel Shader: (This is just a testing shader, it isn't complete)

struct POut
{
	float4 Depth    : SV_Target0;
	float4 Normals  : SV_Target1;
	float4 Lighting : SV_Target2;
};

POut PShader(VOut input)
{
	POut output;

	// Initialize
	output.Depth = float4(0,0,0,1);
	output.Normals = float4(0,1,0,1);
	output.Lighting = float4(0,1,0,1);

	// Depth
	float depth = (input.depthPosition.z / input.depthPosition.w);
	output.Depth = float4(depth, depth, depth, 1);
	if (_alphamap == 1)
	{
		output.Depth.a *= t_alphamap.Sample(ss, input.texcoord).a;
	}
	if (_diffusealpha == 1)
	{
		output.Depth.a *= t_dffalpha.Sample(ss, input.texcoord).a;
	}

	// Normals
	float3 viewSpaceNormalizedNormals = 0.5 * normalize (input.normal) + 0.5; //0.5 * normalize (input.normal) + 0.5
	output.Normals = float4(viewSpaceNormalizedNormals, 1);

	return output;
}

But as I said, only the first render target gets set, the others doesn't, and I don't get why. Am I even setting the render targets correctly?

 

THANKS!

Share this post


Link to post
Share on other sites
Advertisement

Also make sure to create your device with the debug flag, this will tell you if there is any problem.

				UINT createDeviceFlags = 0;
#ifdef _DEBUG
    createDeviceFlags |= D3D11_CREATE_DEVICE_DEBUG;
#endif

				if(FAILED(D3D11CreateDeviceAndSwapChain(nullptr, D3D_DRIVER_TYPE_HARDWARE, nullptr, createDeviceFlags, nullptr, 0, D3D11_SDK_VERSION, &description, &m_pSwapChain, &m_pDevice, &m_featureLevel, &m_pContext)))
					throw d3dException();

You could have some mismatch between your render targets, but my quess is just as good as yours, so check for debug output and PIX is the way to go.

Share this post


Link to post
Share on other sites

When looking at where they are pointing at, all three paths appear black (empty black preview), but I know that one works, the depth mapping (RTV #1). 

 

This is confusing... dry.png

Share this post


Link to post
Share on other sites

Just so you know, the render targets are valid, as when I clear them with, e.g. a red or a green color, it appears in the output, even in pix.

 

But it still appears as if the second and third render targets aren't being written to...

Share this post


Link to post
Share on other sites

Look at the render targets while having selected the draw call that should render to them. what shows up there? Right-click any pixel, and press "debug pixel". Also, try to output explicitely float4(1.0f, 1.0f, 1.0f, 1.0f) to the second and third render target - there might be some issue with your calculations here.

Share this post


Link to post
Share on other sites

When debuggin the first RT, the pixel is written to correctly:

 

Pixel History
Pixel (427, 298) of Render Target 0x069F85B8, Frame 616
 

Initial framebuffer value     Alpha: 0.000 Red: 0.000 Green: 0.000 Blue: 0.000   Event 315: ID3D11DeviceContext::ClearRenderTargetView(0x0BAA5F98, 0x0017F1EC)     Alpha: 1.000 Red: 0.000 Green: 1.000 Blue: 0.000   Event 329: ID3D11DeviceContext::DrawIndexed(36, 0, 0) Primitive 1 of 12

Vertex Shader:0x0BAA5EE8
Debug Vertex 0
Debug Vertex 1
Debug Vertex 2

Geometry Shader:(none)

Pixel Shader:0x0BAA5F40
Debug Pixel (427, 298)
Pixel shader output:   Alpha: 1.000 Red: 0.988 Green: 0.988 Blue: 0.988
Final framebuffer color:   Alpha: 0.000 Red: 0.000 Green: 0.000 Blue: 0.000   Event 329: ID3D11DeviceContext::DrawIndexed(36, 0, 0) Primitive 11 of 12

Vertex Shader:0x0BAA5EE8
Debug Vertex 0
Debug Vertex 1
Debug Vertex 2

Geometry Shader:(none)

Pixel Shader:0x0BAA5F40
Debug Pixel (427, 298)
Pixel shader output:   Alpha: 1.000 Red: 0.988 Green: 0.988 Blue: 0.988
Final framebuffer color:   Alpha: 0.000 Red: 0.000 Green: 0.000 Blue: 0.000   Final framebuffer value     Alpha: 1.000 Red: 1.000 Green: 0.000 Blue: 0.000  

 

But then in the 2nd render target, nothing is there!

 

Same pixel location as in the 1st RT:

 

Pixel History
Pixel (427, 298) of Render Target 0x069F8658, Frame 616
 

Initial framebuffer value     Alpha: 0.000 Red: 0.000 Green: 0.000 Blue: 0.000   Event 317: ID3D11DeviceContext::ClearRenderTargetView(0x0BAA6048, 0x0017F1EC)     Alpha: 1.000 Red: 1.000 Green: 0.000 Blue: 0.000   Final framebuffer value     Alpha: 1.000 Red: 1.000 Green: 0.000 Blue: 0.000  

Share this post


Link to post
Share on other sites

Thats odd. On that same draw-call, look at the device, and inspect its states till you have found the render-target section (don't know which category its under, you should easily find it). Are all render targets still bound at this point in time?

Share this post


Link to post
Share on other sites

I dont know if this is too much to ask for, but maybe one of you guys can write a small mini tutorial with all the steps to create a directx 11 app with multiple render targets, like a small step based tutorial, e.g.:

 

  • Do this...
  • ...
  • Then that

To see if I've done everything right... wacko.png

Share this post


Link to post
Share on other sites

I do believe that all my render targets are valid, as if I change the order of the render targets, it's still the first render target that works.

 

Btw, how can you check the maximum render targets your graphics card supports?

Share this post


Link to post
Share on other sites

The output signature of the pixel shader:

// Output signature:
//
// Name                 Index   Mask Register SysValue Format   Used
// -------------------- ----- ------ -------- -------- ------ ------
// SV_Target                0   xyzw        0   TARGET  float   xyzw
// SV_Target                1   xyzw        1   TARGET  float   xyzw
// SV_Target                2   xyzw        2   TARGET  float   xyzw

After hours in PIX, all the render targets seems to be connected correctly, but when rendering the mesh (PIX has the quite amazing feature where you can see the resources change over time!), still only the first render target gets written to!

Share this post


Link to post
Share on other sites

This is how I initialize each single render target:

D3D11_TEXTURE2D_DESC textureDesc;
	HRESULT result;
	D3D11_RENDER_TARGET_VIEW_DESC renderTargetViewDesc;
	D3D11_SHADER_RESOURCE_VIEW_DESC shaderResourceViewDesc;


	// Initialize the render target texture description.
	ZeroMemory(&textureDesc, sizeof(textureDesc));

	// Setup the render target texture description.
	textureDesc.Width = textureWidth;
	textureDesc.Height = textureHeight;
	textureDesc.MipLevels = 1;
	textureDesc.ArraySize = 1;
	textureDesc.Format = DXGI_FORMAT_R32G32B32A32_FLOAT;
	textureDesc.SampleDesc.Count = 1;
	textureDesc.SampleDesc.Quality = 0;
	textureDesc.Usage = D3D11_USAGE_DEFAULT;
	textureDesc.BindFlags = D3D11_BIND_RENDER_TARGET | D3D11_BIND_SHADER_RESOURCE;
	textureDesc.CPUAccessFlags = 0;
	textureDesc.MiscFlags = 0;

	// Create the render target texture.
	result = device->CreateTexture2D(&textureDesc, NULL, &m_renderTargetTexture);
	if(FAILED(result))
	{
		return false;
	}

	// Setup the description of the render target view.
	renderTargetViewDesc.Format = textureDesc.Format;
	renderTargetViewDesc.ViewDimension = D3D11_RTV_DIMENSION_TEXTURE2D;
	renderTargetViewDesc.Texture2D.MipSlice = 0;

	// Create the render target view.
	result = device->CreateRenderTargetView(m_renderTargetTexture, &renderTargetViewDesc, &m_renderTargetView);
	if(FAILED(result))
	{
		return false;
	}

	// Setup the description of the shader resource view.
	shaderResourceViewDesc.Format = textureDesc.Format;
	shaderResourceViewDesc.ViewDimension = D3D11_SRV_DIMENSION_TEXTURE2D;
	shaderResourceViewDesc.Texture2D.MostDetailedMip = 0;
	shaderResourceViewDesc.Texture2D.MipLevels = 1;

	// Create the shader resource view.
	result = device->CreateShaderResourceView(m_renderTargetTexture, &shaderResourceViewDesc, &m_shaderResourceView);
	if(FAILED(result))
	{
		return false;
	}

	return true;

Share this post


Link to post
Share on other sites

Are you using the second and third Rendertarget after rendering to them as InputTexture for e.g. final combining the image? If so you have to unset the textures from your shaderresources. You can't read and write from and to the same resource at same time. In the first resourceslot you propably using another texture as input.

Share this post


Link to post
Share on other sites

Are you using the second and third Rendertarget after rendering to them as InputTexture for e.g. final combining the image? If so you have to unset the textures from your shaderresources. You can't read and write from and to the same resource at same time. In the first resourceslot you propably using another texture as input.

 

Theoretically true, DX11 will unbind any such resource itself. Try it, set a texture as render target that is still bound to the shader, you should get a warning in debug mode telling you that the shader resource view has been unbound.

 

Some more ideas:

 

- check your blend states. You eigther have to set the blend state manually for each render target, or set independant blend mode to false.

- Check your depth states and / or depth stencil view, I think there is the need to configure it for different render targets explicitely (or at least tell him to only use the setting of the first one) too.

Edited by Juliean

Share this post


Link to post
Share on other sites

Right now, I'm only testing the second, and yes, I unset the resource them after using it.

 

Juliean:

 

The first step fixed it!

 

YAS! laugh.png

 

Thanks!

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