• Advertisement
Sign in to follow this  

DX11 creatInputLayout returns a NULL pointer

This topic is 1700 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 !

// Create our vertex input layout
	D3D11_INPUT_ELEMENT_DESC layout[4];
	layout[0].SemanticName = "POSITION";
	layout[0].SemanticIndex = 0;
	layout[0].Format = DXGI_FORMAT_R32G32B32A32_FLOAT;
	layout[0].InputSlot = 0;
	layout[0].AlignedByteOffset = 0;
	layout[0].InputSlotClass = D3D11_INPUT_PER_VERTEX_DATA;
	layout[0].InstanceDataStepRate = 0;

	layout[1].SemanticName = "TEXCOORD";
	layout[1].SemanticIndex = 0;
	layout[1].Format = DXGI_FORMAT_R32G32_FLOAT;
	layout[1].InputSlot = 0;
	layout[1].AlignedByteOffset = D3D11_APPEND_ALIGNED_ELEMENT;
	layout[1].InputSlotClass = D3D11_INPUT_PER_VERTEX_DATA;
	layout[1].InstanceDataStepRate = 0;

	layout[2].SemanticName = "NORMAL";
	layout[2].SemanticIndex = 0;
	layout[2].Format = DXGI_FORMAT_R32G32B32_FLOAT;
	layout[2].InputSlot = 0;
	layout[2].AlignedByteOffset = D3D11_APPEND_ALIGNED_ELEMENT;
	layout[2].InputSlotClass = D3D11_INPUT_PER_VERTEX_DATA;
	layout[2].InstanceDataStepRate = 0;

	layout[3].SemanticName = "COLOR";
	layout[3].SemanticIndex = 0;
	layout[3].Format = DXGI_FORMAT_R8G8B8A8_UNORM_SRGB;
	layout[3].InputSlot = 0;
	layout[3].AlignedByteOffset = D3D11_APPEND_ALIGNED_ELEMENT;
	layout[3].InputSlotClass = D3D11_INPUT_PER_VERTEX_DATA;
	layout[3].InstanceDataStepRate = 0;

	UINT numElement = ARRAYSIZE( layout ) ;
	if(D3DERR_INVALIDCALL == deviceDX11->CreateInputLayout( layout, numElement, blobVertexGBuffer->GetBufferPointer(), blobVertexGBuffer->GetBufferSize(), &vertexGBufferLayout ))
		return ;

 

The variable "vertexGBufferLayout" has no adress (null pointer), after createInputLayout method. This vraiable is of type ID3D11InputLayout and is in "out" as described in the directx documentation.

 

The associated vertex shader is : 


struct vsIn
{
	float4 position : POSITION ;
	float2 texCoord : TEXCOORD0 ;
	float3 normal   : NORMAL   ;
	float4 color    : COLOR ;
};

struct vsOut
{
	float4 RTposition : POSITION1 ;
	float2 texCoord : TEXCOORD0 ;
	float4 color : COLOR0 ;
	float4 finalPos :SV_POSITION ;
	float3 normal   : NORMAL   ;
	float4 posInLightSpace	 : TEXCOORD1 ;
};

cbuffer globalMatrices
{
	float4x4 WorldView ;
	float4x4 WorldViewProj;
	float4x4 InverseTransposedWorld ;
	//float4x4 lightViewProj ;
}

vsOut vertex_main(in vsIn IN, vsOut OUT)//, in float4 position : POSITION0)
{
	
	//OUT.posInLightSpace = mul(position, lightViewProj); 
	OUT.RTposition = mul(IN.position, WorldView);
	OUT.color = IN.color ;
	OUT.color.w = 1.0 ; 
	//OUT.normal = mul(IN.normal, WorldView);
	OUT.normal = mul(IN.normal, InverseTransposedWorld);
	OUT.texCoord = IN.texCoord ;
	
    OUT.finalPos= mul( IN.position, WorldViewProj );

	return OUT ;
} 

Can you help me ? Did I do something wrong ?

I'm not sure that the pixel format is right as I did, specially for COLOR semantic (is it the right name for colors' semantic ?) where I put DXGI_FORMAT_R8G8B8A8_UNORM_SRGB

Share this post


Link to post
Share on other sites
Advertisement

What does this give you:  ARRAYSIZE( layout );

 

Are blobVertexGBuffer and blobVertexGBuffer valid pointers?

 

And have you tried declaring color without the type DXGI_FORMAT_R8G8B8A8_UNORM_SRGB ?

Share this post


Link to post
Share on other sites

ARRAYSIZE makes a sizeof of the whole array (here the variable named "layout") divided by the sizeof the first element of this array. Here it gives me a size of 4.

blobVertexGBuffer has a valid adress, yes.

I would like to put something else than DXGI_FORMAT_R8G8B8A8_UNORM_SRGB, but I don't know what to put : R8G8B8A8 it's sure, but in float ? UINT ? It is to store colors, and don't know what is appropriate or the most appropriate to store colors from a scene representation.

Share this post


Link to post
Share on other sites

Maybe instead of this:

vsOut vertex_main(in vsIn IN, vsOut OUT)//, in float4 position : POSITION0)
{

 

 
try this:
vsOut vertex_main(in vsIn IN)
{
    vsOut OUT;

 

 

It could work...

Share this post


Link to post
Share on other sites

Not all DXGI formats are supported for use in a vertex buffer. You need to look at the table entitled "Input assembler vertex buffer resources" from here to see which formats are supported. In your particular case the issue is that _SRGB formats aren't supported. You need to use DXGI_FORMAT_R8G8B8A8_UNORM instead, and then apply sRGB->Linear conversion manually in the shader.

Also you should consider turning on the debug device by passing
D3D11_CREATE_DEVICE_DEBUG when creating your device. When you do this, you'll get helpful error messages in your debugger output window whenever you do something wrong.
 

Share this post


Link to post
Share on other sites

vertexGBufferLayout has no value (null pointer), I tried with DXGI_FORMAT_R8G8B8A8_UNORM and vertexGBufferLayout has still no value, I tried also by removing all lines concerning colors in the vertex shader and this code from C++ code :

layout[3].SemanticName = "COLOR";
layout[3].SemanticIndex = 0;
layout[3].Format = DXGI_FORMAT_R8G8B8A8_UNORM_SRGB;
layout[3].InputSlot = 0;
layout[3].AlignedByteOffset = D3D11_APPEND_ALIGNED_ELEMENT;
layout[3].InputSlotClass = D3D11_INPUT_PER_VERTEX_DATA;
layout[3].InstanceDataStepRate = 0;

 

And it still doesn't work sad.png

I tried to put D3D11_CREATE_DEVICE_DEBUG and my program crashes sooner in my code at a place where it usually doesn't crash. And I have no more messages in the output than before. sad.png 

Share this post


Link to post
Share on other sites

Can you show your initialization code for directx 11?

What IDE are you using?

 

Have you tried to initialize your input layout without the Semantic COLOR ?

 

So it would look like this:

 

D3D11_INPUT_ELEMENT_DESC layout[3];
	layout[0].SemanticName = "POSITION";
	layout[0].SemanticIndex = 0;
	layout[0].Format = DXGI_FORMAT_R32G32B32A32_FLOAT;
	layout[0].InputSlot = 0;
	layout[0].AlignedByteOffset = 0;
	layout[0].InputSlotClass = D3D11_INPUT_PER_VERTEX_DATA;
	layout[0].InstanceDataStepRate = 0;

	layout[1].SemanticName = "TEXCOORD";
	layout[1].SemanticIndex = 0;
	layout[1].Format = DXGI_FORMAT_R32G32_FLOAT;
	layout[1].InputSlot = 0;
	layout[1].AlignedByteOffset = D3D11_APPEND_ALIGNED_ELEMENT;
	layout[1].InputSlotClass = D3D11_INPUT_PER_VERTEX_DATA;
	layout[1].InstanceDataStepRate = 0;

	layout[2].SemanticName = "NORMAL";
	layout[2].SemanticIndex = 0;
	layout[2].Format = DXGI_FORMAT_R32G32B32_FLOAT;
	layout[2].InputSlot = 0;
	layout[2].AlignedByteOffset = D3D11_APPEND_ALIGNED_ELEMENT;
	layout[2].InputSlotClass = D3D11_INPUT_PER_VERTEX_DATA;
	layout[2].InstanceDataStepRate = 0;

	UINT numElement = ARRAYSIZE( layout ) ;
	if(D3DERR_INVALIDCALL == deviceDX11->CreateInputLayout( layout, numElement, blobVertexGBuffer->GetBufferPointer(), blobVertexGBuffer->GetBufferSize(), &vertexGBufferLayout ))
		return ;

 

 

And then the shader as the following:

 

struct vsIn
{
	float4 position : POSITION ;
	float2 texCoord : TEXCOORD0 ;
	float3 normal   : NORMAL   ;
};

struct vsOut
{
	float4 RTposition : POSITION1 ;
	float2 texCoord : TEXCOORD0 ;
	float4 color : COLOR0 ;
	float4 finalPos :SV_POSITION ;
	float3 normal   : NORMAL   ;
	float4 posInLightSpace	 : TEXCOORD1 ;
};

cbuffer globalMatrices
{
	float4x4 WorldView ;
	float4x4 WorldViewProj;
	float4x4 InverseTransposedWorld ;
	//float4x4 lightViewProj ;
}

vsOut vertex_main(in vsIn IN, vsOut OUT)//, in float4 position : POSITION0)
{
	
	//OUT.posInLightSpace = mul(position, lightViewProj); 
	OUT.RTposition = mul(IN.position, WorldView);
	OUT.color = float4(1, 1, 1, 1) ;
	OUT.color.w = 1.0 ; 
	//OUT.normal = mul(IN.normal, WorldView);
	OUT.normal = mul(IN.normal, InverseTransposedWorld);
	OUT.texCoord = IN.texCoord ;
	
    OUT.finalPos= mul( IN.position, WorldViewProj );

	return OUT ;
} 

 

 

Just to see if COLOR is the issue.

Edited by Migi0027

Share this post


Link to post
Share on other sites
void D3D11Rendering::initD3DDevice()
{

	D3D_FEATURE_LEVEL  FeatureLevelsRequested = D3D_FEATURE_LEVEL_11_0;
	UINT               numLevelsRequested = 1;


	HRESULT hr = E_FAIL;
	D3D_FEATURE_LEVEL FeatureLevel;

	hr = D3D11CreateDeviceAndSwapChain(NULL, D3D_DRIVER_TYPE_HARDWARE, NULL, D3D11_CREATE_DEVICE_DEBUG, NULL, 0,
		D3D11_SDK_VERSION, &swapChainDesc, &swapChain,  &deviceDX11, &FeatureLevel, &deviceContext );

	if(FAILED(hr))
	{
		return ;
	}
}

 

I guess it was it ?

Share this post


Link to post
Share on other sites

vertexGBufferLayout has no value (null pointer), I tried with DXGI_FORMAT_R8G8B8A8_UNORM and vertexGBufferLayout has still no value, I tried also by removing all lines concerning colors in the vertex shader and this code from C++ code :

layout[3].SemanticName = "COLOR";
layout[3].SemanticIndex = 0;
layout[3].Format = DXGI_FORMAT_R8G8B8A8_UNORM_SRGB;
layout[3].InputSlot = 0;
layout[3].AlignedByteOffset = D3D11_APPEND_ALIGNED_ELEMENT;
layout[3].InputSlotClass = D3D11_INPUT_PER_VERTEX_DATA;
layout[3].InstanceDataStepRate = 0;

 

And it still doesn't work sad.png

I tried to put D3D11_CREATE_DEVICE_DEBUG and my program crashes sooner in my code at a place where it usually doesn't crash. And I have no more messages in the output than before. sad.png 

 

If you are using vs2010, a recent update caused a crash (on device creation if I remember correctly?). You can fix that by installing the remote vs2012 debugging tools (free). see here: http://blogs.msdn.com/b/chuckw/archive/2013/02/26/directx-11-1-and-windows-7-update.aspx
You really should make sure you get the debug runtimes working, it's really helpful, definitely worth the (minimal) effort to setup.

Share this post


Link to post
Share on other sites

well then how do you define your screen width and height if you don't touch the swap chain.

 

Hehe, you're a bit lazy aren't you happy.png

Share this post


Link to post
Share on other sites

I get screen dimensions and affect it then.

For vs2012 tools, thanks i'm downloading it, I come back then to tell you if it works or not.

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