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

Basic structure of a deferred rendering?

6 posts in this topic

Hello, I have some trouble understanding how the basic structure of a deferred rendering solution should be.

 

So this is pretty much where I am.

 

I have one shader with 3 Targets

struct PSOutput
{
  float4 Color : SV_Target0;
  float3 Normal : SV_Target1;
  float3 Specular : SV_Target2;
};

I feel them with stuff. (I can see the different targets in my program as textures and they all look fine).

 output.Color = diffuse*txDiffuse.Sample(samLinear, input.texcoord);
 output.Normal = input.normal;
 output.Specular = specular;

But now the tricky part. If i have understand this correctly I need to send this values in to another shader that does the "deferred lighting calculation", I dont really care about the "calculation" part right now, Im mainly interested in how to structure this.  How do I use/transfer this Targets in to the "light calculation shader".  And do I need render the scene twice, first with basic shader above and then a second time with the "light calculation shader"?

 

Im using Directx11 so any sample in dx11 is much appreciated.

0

Share this post


Link to post
Share on other sites

Hi, thank you for you help so far. Things are a bit clearer now but still :

 

Have understood this correctly? 

1) Render a light geometry, Render the whole scene with all the objects so I can get the correct data in the GBuffers

2) Render a simple 2D quad over the screen with the second shader with all the textures as input (this is you shader example).

3) Combine the two outputs? Not sure if I understand you here, isnt the second shader the final output that will be drawn on the quad?

0

Share this post


Link to post
Share on other sites

Hi, again you help is very much appreciated. 

 

 

2.  Load your buffers into textures and perform lighting equations.  You have a lot of control over how to do this, and people argue about some of the nuances.  For a first shot, I'd honestly just render a fullscreen quad and perform on that.  The result of this shader(s) will be an accumulation buffer of all the light on your rendered geometry.

I have some trouble understanding the lighting equations part of it, not the math itself, more how this is acctually applied in you program. Is this shader applied to a fullscreen quad, and is it excuated for every light you have in the scene, because every light has its own vLightVector and lightIntensity? Or how are you applying this?

0

Share this post


Link to post
Share on other sites

Hi, again you help is very much appreciated. 

 

 

2.  Load your buffers into textures and perform lighting equations.  You have a lot of control over how to do this, and people argue about some of the nuances.  For a first shot, I'd honestly just render a fullscreen quad and perform on that.  The result of this shader(s) will be an accumulation buffer of all the light on your rendered geometry.

I have some trouble understanding the lighting equations part of it, not the math itself, more how this is acctually applied in you program. Is this shader applied to a fullscreen quad, and is it excuated for every light you have in the scene, because every light has its own vLightVector and lightIntensity? Or how are you applying this?

 

 

You're more or less correct here.

Each light is a separate shader pass.  You want to use additive blending to accumulate the contributions of each light into a single light buffer.  Which geometry you use in these shader passes is dependent on what your needs are.  Typically I usually see full-screen quads used for directional lights, spheres used for point lights, and cones used for spotlights, but I've heard talk of screen-aligned bounding boxes too.

Once you've written all of your lights to the light buffer, you do one final shader pass -- a fullscreen quad with samples from your diffuse and light maps multiplied together.

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