Thanks for the link, To make a little update : I've made my own nodevisitor to clone the shared stateset, and it work well and fast. Be carefull : the osgUtil::optimizer share duplicated node/stateset by default...
Thanks for help Regards, Vincent. 2008/12/10 Andreas Lindmark <[EMAIL PROTECTED]> > Tom Forsythe has an entry on his blog about the cost of state changes that > I've found to be very helpful. > > http://home.comcast.net/~tom_forsyth/blog.wiki.html<http://home.comcast.net/%7Etom_forsyth/blog.wiki.html> > > /Andreas > > 2008/12/9 Paul Melis <[EMAIL PROTECTED]> > > Tomlinson, Gordon wrote: >> >>> Hi Vincent >>> Of the top of my head I would assume it an optimizer that's without >>> looking at the code >>> as generally you want to optimize and share states as state changes is >>> one of the big hurts >>> in the OGL pipe line >>> >> Not really on-topic, but I always wondered if there is some kind of >> overview of which OpenGL state changes are more expensive than others. E.g. >> setting the new current color is almost certainly cheaper than making a >> different 2D texture active. Browsing through the OSG code I couldn't really >> pinpoint where such an order is assumed. >> >> Regards, >> Paul >> >> _______________________________________________ >> 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 > >
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
