# DX11 [SlimDX] Problems Creating InputLayout in DirectX 11

This topic is 2868 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

## Recommended Posts

I'm using the MiniTri D3D11 sample that's in the repository (DX11 branch), I've updated all of the code to match the changes made since that was written and the latest SDK (Feb 2010). I'm having difficulty creating an InputLayout from the MiniTri.fx vertex shader however. Relevant code is below:
string errors;

{
Layout = new D3D11.InputLayout(Device, s, inputElements);
}


The code breaks on the "Layout = ..." line, with the following error in my output window:
D3D11: ERROR: ID3D11Device::CreateInputLayout: Encoded Signature size doesn't match specified size. [ STATE_CREATION ERROR #161: CREATEINPUTLAYOUT_UNPARSEABLEINPUTSIGNATURE ]
Unfortunately, I don't have a clue what that means, and Google hasn't been too helpful so far either. For reference, the MiniTri.fx file is as follows:
struct VS_IN
{
float4 pos : POSITION;
float4 col : COLOR;
};

struct PS_IN
{
float4 pos : SV_POSITION;
float4 col : COLOR;
};

PS_IN VS( VS_IN input )
{
PS_IN output = (PS_IN)0;

output.pos = input.pos;
output.col = input.col;

return output;
}

float4 PS( PS_IN input ) : SV_Target
{
return input.col;
}

technique10 Render
{
pass P0
{
}
}


[Edited by - adt7 on March 7, 2010 2:11:46 PM]

##### Share on other sites
Still no joy on this. I realise I left out the contents of the inputElements variable in my above post:

            D3D11.InputElement[] inputElements = new SlimDX.Direct3D11.InputElement[]                        {                                new D3D11.InputElement("POSITION",0,DXGI.Format.R32G32B32A32_Float,0,0),                                new D3D11.InputElement("COLOR",0,DXGI.Format.R8G8B8A8_UNorm,16,0)                        };[/lang]

##### Share on other sites
Does your effect file perhaps have a Unicode encoding? That always causes all sorts of strange errors to occur.

##### Share on other sites

But isn't DXGI.Format.R8G8B8A8_UNorm an integer format?
and your color is actually a float4?

Shouldn't it be DXGI.Format.R32G32B32A32_Float in your InputElements?

edit:
ie:
new D3D11.InputElement("COLOR",0,DXGI.Format.R32G32B32A32_Float,16,0)

##### Share on other sites
Quote:
 Original post by Mike.PopoloskiDoes your effect file perhaps have a Unicode encoding? That always causes all sorts of strange errors to occur.

Nope. It's copied straight from the repository.

I've tried saving one out from Notepad with ANSI encoding and still the same problem.

Don't Unicode .fx files normally throw errors at compile time? Rather than when using the result of the compile?

Quote:
 Original post by LostIchiNewbie here so please beware of the advice :p.But isn't DXGI.Format.R8G8B8A8_UNorm an integer format?and your color is actually a float4?Shouldn't it be DXGI.Format.R32G32B32A32_Float in your InputElements?edit:ie:new D3D11.InputElement("COLOR",0,DXGI.Format.R32G32B32A32_Float,16,0)

I thought that might be a problem (not that it should be) and have tried this already, same deal.

##### Share on other sites
This is frustrating the hell out of me now.

Someone must be using DirectX 11 with SlimDX, or it must have at least been tested by the SlimDX guys.

Is there not an updated MiniTri sample for DirectX 11 out there?

How else am I meant to create a valid ShaderSignature to be used to generate an InputLayout without using the Effects framework from SlimDX.Direct3D10?

EDIT: The files I'm working with can be found here.

[Edited by - adt7 on March 8, 2010 5:16:06 AM]

##### Share on other sites
Quote:
 Original post by adt7Is there not an updated MiniTri sample for DirectX 11 out there?

Yes, it is indeed a shame that there isn't a MiniTri11 example included in the SlimDX SDK. I think its pretty essential.
I've updated MiniTri10 to work with DX11. You can find it here:

http://pastebin.com/xW21pnG4

Just use the FX file from the MiniTri10 example.

##### Share on other sites
Thanks a lot for that. Rating++.

I didn't realise that using "dummy" in the Effect constructor would allow you to compile a SlimDX.Direct11.Effect, I simply saw the parameter and figured it was the same as when compiling a Vertex Shader/Pixel Shader separately and that didn't work when I tried it.

Now to get on with some actual work!

Although this still doesn't solve the fact that the InputLayout ctor is throwing up an error with what should be valid input.

[Edited by - adt7 on March 8, 2010 9:34:20 AM]

##### Share on other sites
Apologies for bumping this again, but I'm hoping it'll catch one of the SlimDX guy's eye again.

As said already, I've started making some progress by using Effects rather than trying to produce seperate VertexShader and PixelShader objects, however, ideally, this is what I want to be able to do.

So, is there a reason why the InputLayout ctor is failing with what I assume is a valid ShaderSignature (it is produced from valid bytecode, so it should be, and no exception or errors appear on creation) from a compiled VertexShader?

##### Share on other sites
Bringing this back up for the weekend.

##### Share on other sites
Does it work if you remove the color, and only use a single input element for position?

• ### Similar Content

• 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

• 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.

Also, for reference, here's tutorial #40 which has normal shadows but no blur, which I also ported, and it works perfectly.

• By xhcao
Is Direct3D 11 an api function like glMemoryBarrier in OpenGL? For example, if binds a texture to compute shader, compute shader writes some values to texture, then dispatchCompute, after that, read texture content to CPU side. I know, In OpenGL, we could call glMemoryBarrier before reading to assure that texture all content has been updated by compute shader.
How to handle incoherent memory access in Direct3D 11? Thank you.
• By _Engine_
Atum engine is a newcomer in a row of game engines. Most game engines focus on render
techniques in features list. The main task of Atum is to deliver the best toolset; that’s why,
as I hope, Atum will be a good light weighted alternative to Unity for indie games. Atum already
has fully workable editor that has an ability to play test edited scene. All system code has
simple ideas behind them and focuses on easy to use functionality. That’s why code is minimized
as much as possible.
Currently the engine consists from:
- Scene Editor with ability to play test edited scene;
- Powerful system for binding properties into the editor;
- Render system based on DX11 but created as multi API; so, adding support of another GAPI
is planned;
- Controls system based on aliases;
- Font system based on stb_truetype.h;
- Support of PhysX 3.0, there are samples in repo that use physics;
- Network code which allows to create server/clinet; there is some code in repo which allows
to create a simple network game
I plan to use this engine in multiplayer game - so, I definitely will evolve the engine. Also
I plan to add support for mobile devices. And of course, the main focus is to create a toolset
that will ease games creation.
Link to repo on source code is - https://github.com/ENgineE777/Atum
Video of work process in track based editor can be at follow link:

• I made a spotlight that
1. Projects 3d models onto a render target from each light POV to simulate shadows
2. Cuts a circle out of the square of light that has been projected onto the render target
as a result of the light frustum, then only lights up the pixels inside that circle
(except the shadowed parts of course), so you dont see the square edges of the projected frustum.

After doing an if check to see if the dot product of light direction and light to vertex vector is greater than .95
to get my initial cutoff, I then multiply the light intensity value inside the resulting circle by the same dot product value,
which should range between .95 and 1.0.

This should give the light inside that circle a falloff from 100% lit to 0% lit toward the edge of the circle. However,
there is no falloff. It's just all equally lit inside the circle. Why on earth, I have no idea. If someone could take a gander