• 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
Yours3!f

GLSL fragment shader, prevent depth writing

4 posts in this topic

Hi,

 

is there any way to prevent OGL to write the depth buffer from the fragment shader? I'm thinking of something like discard.

I'd like to throw away pixels whose alpha is not big enough. This would help me to perform early depth testing to reduce overdraw.

Node that this is a 2D engine, so all of this are basically sprites.

 

Best regards,

Yours3lf

Edited by Yours3!f
0

Share this post


Link to post
Share on other sites

Early depth testing is very efficient (nothing even remotely as efficient can be done in shader) - mucking with the depth in fragment shader will turn early depth test off (because there is no depth early available to do anything with ... early).

 

You can not disable depth writes in fragment shader - just discard the fragment completely (the "discard" you mentioned) omitting the depth write also.

 

Newer OGL versions might provide something that could be of use tho (but i doubt it) - i rarely use anything above OGL3.3.

1

Share this post


Link to post
Share on other sites

That won't work. You have only 3 legitimate options:

  • disable depth writes (using the GL API, not in GLSL) -- this will not write depth for any pixel
  • don't write to gl_FragDepth in your shader (not at all) -- this will use the interpolated depth instead
  • discard -- this will kill the fragment, including depth (but also color)

 

Writing to gl_FragDepth for some fragments and not doing it for some others is theoretically possible, but a shader doing so is not well-formed. The outcome is undefined.

 

To throw away pixels that you don't want, I'd just discard, that's what it's for. It discards the color value, nothing is written out.

Edited by samoth
1

Share this post


Link to post
Share on other sites

thanks both of you. I tried it out, and the results I got was:
-when early depth testing is enabled: layout(early_fragment_tests) in;
the whole sprite is overwritten the by topmost (despite the black areas being discarded, see pic)
-if disabled it works fine.
 

so I'd like to overcome this. Any ideas?

Edited by Yours3!f
0

Share this post


Link to post
Share on other sites

thanks both of you. I tried it out, and the results I got was:
-when early depth testing is enabled: layout(early_fragment_tests) in;
the whole sprite is overwritten the by topmost (despite the black areas being discarded, see pic)
-if disabled it works fine.

Weird :/.

Generally, if early depth test is possible then it will be done - there is no reason to ask for it (funky exceptions, which i am not aware of, excepted). When explicitly requiring it causes "discard" to be ignored then ... that is a strong suggestion that early depth test is impossible given the shader.

Discard is similar to alpha testing - it sounds like your hardware just does not support early depth test with alpha testing. When i think about it then it rings true - i vaguely remember that alpha test indeed is not compatible with early depth test.

Logically it is also true - depth test and write happen at the same time, it can not do that early if the alpha test/discard result is only known after the fragment program ran.

In short: cannot use early depth test.

So, bac to: Why do you need it ... really? What platform are you on that it is an concern? How do you know the overdraw is a problem? Is discard without early depth test really too slow? Could you perhaps simplify your shader?

edit:
Wiki agrees with me: http://www.opengl.org/wiki/Early_Fragment_Test Edited by tanzanite7
0

Share this post


Link to post
Share on other sites

thanks both of you. I tried it out, and the results I got was:
-when early depth testing is enabled: layout(early_fragment_tests) in;
the whole sprite is overwritten the by topmost (despite the black areas being discarded, see pic)
-if disabled it works fine.

Weird :/.

Generally, if early depth test is possible then it will be done - there is no reason to ask for it (funky exceptions, which i am not aware of, excepted). When explicitly requiring it causes "discard" to be ignored then ... that is a strong suggestion that early depth test is impossible given the shader.

Discard is similar to alpha testing - it sounds like your hardware just does not support early depth test with alpha testing. When i think about it then it rings true - i vaguely remember that alpha test indeed is not compatible with early depth test.

Logically it is also true - depth test and write happen at the same time, it can not do that early if the alpha test/discard result is only known after the fragment program ran.

In short: cannot use early depth test.

So, bac to: Why do you need it ... really? What platform are you on that it is an concern? How do you know the overdraw is a problem? Is discard without early depth test really too slow? Could you perhaps simplify your shader?

edit:
Wiki agrees with me: http://www.opengl.org/wiki/Early_Fragment_Test

 

thanks for clarifying. Seems like I can't use early depth testing like this :/
Well I thought that I could eliminate overdraw by doing it. I plan to create a 2D game and if lots of effects will be going on at the same place it would kill the frame rate.
something like this: http://www.youtube.com/watch?v=iubNpqp41Cs
It is not a performance concern now, it will be if there are lots of overlapping thing in the scene, as I'm using a simple lightweight deferred system for lighting. And since early depth testing is usually used in such systems I thought I'd give it a try.

For now only draw calls are a problem, but I'll solve it by instancing.
I thought about a depth pre-pass pass :) but that would require evaluating the fragment shader, which is not good.

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