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

Device Context and Vertex Buffer with Many Vertex and Pixel Shaders

7 posts in this topic

Hello!

 

I have tried to phrase my question in multiple ways, mostly because I don't think I understand the complexity of this particular topic, so thanks for your patience!

 

Yet another rephrase:

1. Can I write Vertex Data to the VertexBuffer for two different objects, (square, triangle), with either the same or different input layout?
2. Can they both use different vertex shaders, pixel shaders, and textures?

3. Could I write a sort of Shader Selector in HLSL that reads a parameter from the input element and dynamically chooses a different pixel shader or texture?

 

Related C++ Code

 

When I create an input layout, can I do this without specifying an actual Vertex Shader, or somehow specify more than one?

 

 

    NS::ThrowIfFailed(
    result = NS::DeviceManager::Device->CreateInputLayout(
    NS::ModelRenderer::InitialElementDescription,
    2,
    vertexShaderFile->Data,
    vertexShaderFile->Length,
    & NS::ModelRenderer::StaticInputLayout
    )
    );


 

When I set the VertexShader and PixelShader, how do I associate them with a particular model in my VertexBuffer?  Is it possible to set more than one of each?

?

  DeviceManager::DeviceContext->IASetInputLayout(ModelRenderer::StaticInputLayout.Get());

DeviceManager::DeviceContext->VSSetShader(ModelRenderer::StaticVertexShader.Get(), nullptr, 0);
DeviceManager::DeviceContext->PSSetShader(ModelRenderer::StaticPixelShader.Get(), nullptr, 0);
Edited by e.s.
0

Share this post


Link to post
Share on other sites

you need to pass a pointer to the compiled bytecode of a vertex shader in order to create an input layout.

 

Just a few* questions for clarification, if you don't mind:  (I also cleaned up my initial question.)

 

Are there any issues with passing in a null pointer?

 

If I use multiple draw calls for models that require different shaders, do I just release the buffer, bind all the new vertex instance data, and draw?  Or do I have to re-bind/re-set all of my shaders as well since the input layouts will be different?

 

DrawInstanced allows you to effectively point at a different model template in one buffer, and instance info for that model from another to render the model + instance data. 

 

Is it possible to have the VertexShader define multiple output types so that a different pixel shader could be called?

 

Thanks for your help!

Edited by e.s.
0

Share this post


Link to post
Share on other sites

You can't pass in a NULL pointer, you need to pass in a pointer to the bytecode. The whole point of an input layout is to create a binding between the contents of a vertex buffer and a vertex shader's input signature, if you didn't pass a pointer to the VS bytecode there would be nothing to bind to. There are certain cases where you don't need an input layout at all (basically whenever the vertex shader doesn't actually expect any inputs from a vertex buffer), but that's about it.

I'm not sure if I understand your second question..

 

Your vertex shader only has one set of outputs, which is the outputs that are declared in the shader when you compile it. If you need a different set of outputs, then you need to compile a different vertex shader.

0

Share this post


Link to post
Share on other sites

Thanks, I am just trying to find the most efficient way to have different pixel shaders used by the same type of mesh, but colored differently.  For example, I would like square and triangle models in the vertex buffer, and for the pixel shaders to act differently based on instance data....

 

Is there a good way to accomplish this?

Edited by e.s.
0

Share this post


Link to post
Share on other sites

You could use the same pixel shader, and then in your instance data you could pass a color along with the transform. Then you can pass that color from the vertex shader to the pixel shader, and use that as the output color.

0

Share this post


Link to post
Share on other sites

To answer  all 3 of your questions, you can only ever have 1 shader bound for each stage. ..

 

What do you mean by stage?  I was thinking that a Vertex Shader /was/ a stage.  I am trying to bind 3 vertex shaders via the input layout, (which apparently won't work), or at least 3 shaders into the DeviceContext, using VSSetShader .... Can there only ever be 1 shader "pipeline"  per DeviceContext?

0

Share this post


Link to post
Share on other sites

"Stage" as in "vertex shader stage", "pixel shader shader stage", etc. In other words, you can only ever have 1 shader of each type bound to a context at any given time.

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