Jump to content
  • Advertisement
Sign in to follow this  
kRogue

OpenGL FBO - question

This topic is 4121 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

As I read through the FBO spec and Gamedev's tutorial, I did not see how to do this with FBO: Draw to Multiple Color Buffers but use the "default" depth and or stencil buffers, i.e. I want the render to texture only the color stuff, but I want the depth and stencil values to be the "usual" openGL depth and stencil buffers... to do this, do I just not attach a depth and stencil render object, or do I have to do something to make sure that "the standard openGL" depth and stencil buffers are the one drawn to, or is this not possible?

Share this post


Link to post
Share on other sites
Advertisement
You can't do that. You still need to attach a depth/stencil buffer for the FBO. Using the framebuffers depth/stencil is not possible.

Share this post


Link to post
Share on other sites
I started to figure that since if it was possible to use the stencil and framebuffer from the window system, then the FBO would have to be the same resolution as the window you asked for, not to mention all the mess associated to "pixel ownership test", since it always is supposed to pass for FBO, but the windowing system decides in the case of non-FBO, so atleast it makes sense... sigh...

Share this post


Link to post
Share on other sites
Some of us requested this while the spec was being written and the ARB was requesting feedback. If the framebuffer is large and your FBO is small, why not use the framebuffer depth-stencil?

So, it's just simpler to allocate some depth/stencil for the FBO and perhaps they will make a new extension for being able to do that.... case closed :)

Share this post


Link to post
Share on other sites
It would be nice if there was an extension to the FBO spec where one can specify a sub region of the framebuffer to be used for rendering, but this can run badly afoul with the pixel ownership test which happens before anything (the windowing system decides this test), so the danger is that if you used a portion of the framebuffer that was obscured, then the results at that portion are undefined, which would be a bad thing for the whole "render to texture" mentality (this is the main reason why glCopy is not good enough).. though that in itself for color buffers is not as a big deal, but for stencil and depth buffers... it can create very strange hard to track bugs in windowed GL apps.... oh well... no real big deal at the end of the day...except the possibly wasted memory: one depth and stencil buffer per different resolution of FBO's (because a fixed depth or stencil buffer can be shared between FBO's)...

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!