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

Deferred Shading troubles

4 posts in this topic

Hello,

I am trying to implement deferred shading but I ran into one issue. But first, some background details.

All the buffers:[list=1]
[*]SwapChain; R8G8B8A8_UNORM
[*]Depth Stencil; R32_TYPELESS
[*]Color Buffer; R8G8B8A8_UNORM
[*]Depth Buffer (linear); R32_FLOAT
[*]Normals Buffer; R8G8B8A8_UNORM (accuracy might be low, but it doesn't matter at this point)
[/list]

Rendering loop:[list=1]
[*]I use ID3D11DeviceContext::OMSetRenderTargets() to set #3, #4, #5 as render targets and #2 as depth stencil.
[*]Draw all geometry: unshaded color goes into #3, normals into #5, vertex shader outputs transformedPosition.z, pixel shader divides it by far plane to normalize it.
[*]Using ID3D11DeviceContext::OMSetRenderTargets() setting #1 as render target, no depth stencil
[*]#3 and #5 are set as shader resources
[*]Performing phong shading
[/list]
However, I'd also like to have FXAA (or any other post-process antialiasing), however it'll require #1 as input, where do I output then?
It seems wrong to output into #3 and then copy back to #1. How can this be solved?

Thank you in advance.
0

Share this post


Link to post
Share on other sites
Post-processing is mostly done by rendering to another render target texture, you don't write it back into the G-Buffer since the G-Buffer is solely meant for storing actual data about your geometry and because it could be required for other post-processing steps.

When you're done with post-processing you can write out the contents of your last post-processing step's render target to your actual back buffer, or you could just set your back buffer as the render target for your last step.
1

Share this post


Link to post
Share on other sites
[quote name='Radikalizm' timestamp='1344373269' post='4967142']
Post-processing is mostly done by rendering to another render target texture, you don't write it back into the G-Buffer since the G-Buffer is solely meant for storing actual data about your geometry and because it could be required for other post-processing steps.
[/quote]
I'm unsure I understood you correctly, please tell me if I'm wrong.
So I have to keep Color, Depth and Normal Buffers unmodified at all times, perform phong shading and output result into extra RT #1, then perform antialiasing and output into extra RT #2, and then copy from extra RT #2 to backbuffer? Isn't it a bit memory waste keeping one extra RT for each pass?
0

Share this post


Link to post
Share on other sites
[quote name='Ripiz' timestamp='1344411378' post='4967289']
[quote name='Radikalizm' timestamp='1344373269' post='4967142']
Post-processing is mostly done by rendering to another render target texture, you don't write it back into the G-Buffer since the G-Buffer is solely meant for storing actual data about your geometry and because it could be required for other post-processing steps.
[/quote]
I'm unsure I understood you correctly, please tell me if I'm wrong.
So I have to keep Color, Depth and Normal Buffers unmodified at all times, perform phong shading and output result into extra RT #1, then perform antialiasing and output into extra RT #2, and then copy from extra RT #2 to backbuffer? Isn't it a bit memory waste keeping one extra RT for each pass?
[/quote]

That's basically how I do this yes, and I assume that's how it's done in most of the cases. You could avoid wasting memory by re-using RTTs when possible, but this becomes more difficult when you need more 'exotic' texture formats for specific purposes or differently sized render targets, which you will definitely need once you get to more advanced effects. Another problem with re-using RTTs could arise when you have to run different branches of post-processing effects which need to be combined together as you have to make sure that the contents of certain RTTs don't get invalidated.

Experiment with it a bit and see what works out for you
It comes down to doing a good amount of profiling I suppose Edited by Radikalizm
1

Share this post


Link to post
Share on other sites
[quote name='Ripiz' timestamp='1344411378' post='4967289']
then perform antialiasing and output into extra RT #2, and then copy from extra RT #2 to backbuffer? Isn't it a bit memory waste keeping one extra RT for each pass?
[/quote]

There's no need to perform antialiasing into a second extra render target and then copy it to the backbuffer. You can just apply the antialiasing as you write to the back buffer.
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