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

InputLayouts

7 posts in this topic

Hello!

 

I'm currently writing input layout manager. Well the problem is ... 

 

 

d3ddev->CreateInputLayout(inputElemDesc.get(), numSemantics, 
pShader->GetShaderBlob().GetBufferPointer(), <------------------------------------ HERE
pShader->GetShaderBlob().GetBufferLength(), 
&m_pD3D11Layout);
 
The result is 'success' against that shader :

float4 main(
): SV_Position
{
float4 retval = float4(0.f, 0.f, 0.f, 1.f);
 
return retval;   
}
 
But when i try to Draw something that error occurs : "  Signatures between stages are incompatible. The input stage requires Semantic/Index (POSITION,0) as input, but it is not provided by the output stage. "
 
inputElemDesc is containing the 'POSITION' Semantic (only) but the shader compiler is cutting it! (the format is r32g32b32_FLOAT)
 
I can't compile shaders online(because of hardware limitations), so i cannot generate dummy shader for each inputlayout... 
 
Any suggestions?
 
0

Share this post


Link to post
Share on other sites

I went through something like like this. Make sure you are using the same structs with the exact same semantics for each shader stage. I had an issue where I was toying with my vertex shader output struct and forgot to also change my other shaders to match.

Edited by cephalo
0

Share this post


Link to post
Share on other sites

So, where does your shader signature require position? Are you sure you've the right shader bound to the pipeline while submitting the drawcall?

1

Share this post


Link to post
Share on other sites

Yes im shure that evrything about the shader and inputElementDesc is OK. The problem is that im validating the inputLayout(with position only) against the shader that doesn't require any input. The layout is created succefully. After that im using the same input layout with shader that requires POSITION . The error message is : "Signatures between stages are incompatible. The input stage requires Semantic/Index (POSITION,0) as input, but it is not provided by the output stage." 

Actually the input layout provides the position semantic, but obviously it is illigal to  validate input layout against shader without any input rquirements.
I want to find a way to validate my input layout. I think that InputLayouts must be build for the mesh object not for ther shader. That thing is driving me crazy!!!

Well actually there is one solution (witch i cannot use): to create on the fly vertex shader based no the input layout, but because of platform limitations I cannot compile shader at runtime(windows phone and (im not shure about it) Xbox). 

 

0

Share this post


Link to post
Share on other sites

I can't compile shaders online(because of hardware limitations), so i cannot generate dummy shader for each inputlayout... 

 

Most practical method is to validate the input layout against an actual shader that uses the input layout.

 

When binding an input layout together with a vertex shader, the layout needs to have (validated) element for all the VS' input elements (matching in position and order). It can have additional element used by other shaders, but it can never omit elements required by the shader.

 

For example, if you have an input layout that's validated against a shader that uses the input elements [POSITION, NORMAL, UV], the layout can be used to feed the following shader input structs: [POSITION, NORMAL, UV] [POSITION, NORMAL] [POSITION] [-]. (You'd validate such an input layout against the shader that has the largest span of input elements.)

1

Share this post


Link to post
Share on other sites

Using multiple streams would add some overhead (for both the API and the Input Assembler). This will increase with the number of semantics used.

0

Share this post


Link to post
Share on other sites

Splitting vertex-data in multiple streams can be very handy if you don't want to always provide the full amount of vertex information. Let's say you want to do a z-prepass, you don't need information like normal/tangent, color etc... The proposed solution however can easily result in a huge number of simultaneous bound vertex streams and thus can badly impact IA fetch performance.

1

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