[Mesa-dev] FBO read / draw completeness.

[Eric Anholt]

On Fri, 22 Apr 2011 14:19:04 +0200, Henri Verbeet <hverbeet at gmail.com> wrote:
> Hi,
> 
> A while ago we talked on IRC about the FBO completeness rules for read
> / draw FBOs.
> 
> The specific bug that triggered that was that Mesa only applies
> ReadBuffer() calls to the read FBO and DrawBuffers() to the draw FBO.
> This means that if you're trying to do a depth blit using
> BlitFramebuffer() (and set both the read and draw buffers to NONE),
> you're going to get an incomplete draw buffer on the read fbo, and an
> incomplete read buffer on the draw FBO, because both of those are
> still set to the default COLOR_ATTACHMENT0.
> 
> The other, somewhat more hypothetical example was doing a
> BlitFrambuffer() from a read FBO with just a COLOR0 attachment to the
> second attachment of a draw FBO with both COLOR0 and COLOR1
> attachments. This would currently work, but more by accident than
> anything else.
> 
> I think the things that came out of that conversation were the following:
>   - ARB_ES2_compatibility / GL4.1 will make all of this just go away
> by ignoring read / draw buffers for FBO completeness.

ARB_ES2_compatibility is already landed, so the point should be moot
now, right?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/mesa-dev/attachments/20110422/317f099c/attachment.pgp>