HI Vincent, The frame lag is an unfortunate side effect to the way that osgFX doesn't know how to render itself until it's queried the OpenGL extensions/versions available.
osgFX is rather old now and code do with a revamp that addresses this issues, but would need a form of up front extension checking that requires a valid graphics context, so it rather pushes the current decoupled design where the scene graph doesn't get involved with construction of contexts. Feel free to dive in and come up with a proposal. Robert. On Wed, Feb 10, 2010 at 3:07 PM, Vincent Bourdier <[email protected]> wrote: > Hi all, > > This a very strange and unexpected bug : > > Applying an osgFX::Scribe effect on a node, we can see a lag in the render : > If you get each frame a screenshot you can see : > > *Frame #1* > Action : no action > Render : normal render of the node > > *Frame #2* > Action : adding a osgFX::Scribe node as parent of the node to apply the > effect (done in a callback on root node) > Render : no node ! > * > Frame #3* > Action : no action > Render : node with applied effect. > > > So during one frame, the node is not rendered at all... This is very > embarrassing if you take a screenshot automatically in post-render of the > frame where > you apply the effect... > > > Thanks for your help. > > Regards, > Vincent > > > __________ Information from ESET NOD32 Antivirus, version of virus signature > database 4854 (20100210) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
