Hi Aurelien, Thanks for the fix, now merged with svn/trunk and OSG-3.2 branch. For this check-in I didn't merge the glCheckFramebufferStatus lines in case they result in a stall. I do think it would be a useful check to have though, perhaps we could only do the check if fine grained GL error checking is enabled in osg::State?
Robert. On 22 November 2013 12:30, Aurelien Albert <[email protected]>wrote: > Hi, > > In the "apply" method of osg::FrameBufferObject, the draw buffers are > always enabled, even if the target is only "READ_FRAMEBUFFER". > > This can lead to inconsistency if you bind a framebuffer with multiple > attachments in DRAW mode and then a framebuffer with different attachment > count in READ mode (for example to manually "blit" from a FBo to another). > > On some ATI cards (at least RADEON HD) this also leads to an "incomplete " > FBO status > > I've added a test to enable drawbuffers only if target is "DRAW" or > "READ_DRAW", this solves my problems on ATI cards. > > I've also added a "glCheckFramebufferStatus" call (this is how I > discovered the origin of my problem), but I'm not sure if this is realy a > great idea because it may lead to a complete OpenGL pipeline stall to check > the FBO status. > > > Cheers, > Aurelien > > ------------------ > Read this topic online here: > http://forum.openscenegraph.org/viewtopic.php?p=57396#57396 > > > > > _______________________________________________ > osg-submissions mailing list > [email protected] > > http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org > >
_______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
