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

Pipeline Configuration for Post-Processing Shaders

4 posts in this topic

Hello all,

 

This is a new concept for me, so I apologize if I come across as short-sighted or noobish,

I am writing a post-process shader that will take a scene that has been rendered to a texture and blur it.

Since this blur shader only operates on the texture, there is no need for a Vertex Shader.

 

So, How do I configure the Pipeline?

 

I know with a typical effect, you usually have two shaders, a Vertex Shader and a Pixel Shader.

So I would prime the API like so,

 

d3dContext->IASetInputLayout("Parameters");

d3dContext->IASetIndexBuffer("Parameters");

d3dContext->IASetVertexBuffer("Parameters");

d3dContext->IASetPrimitiveTopology("Parameters");

 

d3dContext->VSSetShader();

d3dContext->PSSetShader();

 

///////////////////////////////////////////////////////////////////////////

//Binding of worldViewProj Matrices and assests to their respective Constant Buffers

////////////////////////////////////////////////////////////////////////////

 

And then eventually,

 

d3dContext->draw || d3dContext->DrawIndexed();

 

But with only a pixel shader, I would only need to do this, maybe?

 

d3dContext->IASetInputLayout("Parameters");

d3dContext->PSSetShader();

d3dContext->PSSetShaderResources();

 

d3dContext->Draw();

 

But what would I be drawing! If I don't have a vertex shader I don't need to submit a vertex or index buffer. Nor any of the corresponding matrices.

 

If I don't have a VertexBuffer submitted to D3D, I wouldn't expect the draw call to do anything.

 

But if I don't make this call: d3dContext->Draw();

How is this shader to be executed?

 

I guess i'm asking is how to execute a post-process shader or point me if possible in the right direction for learning how to utilize post-process shaders

 

Thansk for any replies!

 

Marcus

 

 

0

Share this post


Link to post
Share on other sites
You still need a vertex shader - the geometry is a quad or triangle that covers your entire screen!

To work without any geometry at all, you'd use a compute shader instead of a pixel shader, an Dispatch instead of Draw.
2

Share this post


Link to post
Share on other sites

You still need a vertex shader - the geometry is a quad or triangle that covers your entire screen!

To work without any geometry at all, you'd use a compute shader instead of a pixel shader, an Dispatch instead of Draw.

tongue.png It's been a looooong day.

 

I knew better, thank you so much.

 

Marcus

Edited by markypooch
0

Share this post


Link to post
Share on other sites

Drawing without a vertex buffer is a common idiom for fullscreen quads.  See Using the Input-Assembler Stage without Buffers on MSDN for a description and sample code.

Very informative. So Really for my simple Post-Process Shader, I can pretty much skip Buffer submission to D3D and just define my quad in the Vertex Shader...I Like it!

 

I guess my orginal thought regarding Post-Processing is more akin to utilitizing a Compute Shader (Don't know why at the time I thought no Geometry would be involved, It was a looooong day yesterday!)

 

Thanks for the replies, and sorry for the newebish question. it did give me some interesting ideas!

 

Marcus

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