• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
Hornsj3

Why Does CreateInputLayout Work With This Descriptor?

2 posts in this topic

So I'm playing around with the Input Layout stage of the pipeline and I have a question.

Here's my Input Layout descriptor element
[CODE]
D3D11_INPUT_ELEMENT_DESC inputLayoutDesc[] =
{
{
"TEXCOORD", //Semantic name
0, //Semantic Index
DXGI_FORMAT_R32G32_FLOAT, //DXGI Format
0, //Input Slot
D3D11_APPEND_ALIGNED_ELEMENT, //Number of bytes from start of array to this element
D3D11_INPUT_PER_VERTEX_DATA, //Input Classification (we are using per vertex not per instance data)
0 //Instance data step rate, 0 for Per-Vertex data
},
{
"POSITION", //Semantic name
0, //Semantic Index
DXGI_FORMAT_R32G32B32_FLOAT, //DXGI Format
0, //Input Slot
D3D11_APPEND_ALIGNED_ELEMENT, //Number of bytes from start of array to this element
D3D11_INPUT_PER_VERTEX_DATA, //Input Classification (we are using per vertex not per instance data)
0 //Instance data step rate, 0 for Per-Vertex data
},

};
[/CODE]


Here's my Vertex Shader
[CODE]
struct VS_INPUT
{
float3 Pos : POSITION0;
};
struct PS_INPUT
{
float4 Pos : SV_POSITION; //Screen-space position
};

PS_INPUT VS(VS_INPUT input)
{
PS_INPUT output = (PS_INPUT)0;
output.Pos = float4(input.Pos, 1.0f);

return output;
}
[/CODE]


This works fine...meaning I am able to create my input layout object and set it to the input assembler stage.

My question is, why does this work?

From what I have read the input layout has to match the vertex shader input signature. This clearly does not. It seems to me as long as it can match the Position semantic it will allow me to create the object and set it.

It seems like this should not work because it does not exactly match the expected input to the vertex shader.
0

Share this post


Link to post
Share on other sites

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  
Followers 0