HI Adrian, This issue doesn't haven't anything today with the pager. If you osg::Geometry is dropping down to use a GLBeginEndAdapter then it's on an OpenGL slow path which will be inefficient.
Please check you database for possible places where the osg::Geometry in it drop everything off use of straight vertex arrays. Per primitive bindings and vertex indices are all going to force slow dispatch to OpenGL. These elements in the OSG are only maintained for backwards compatibility and I strongly recommend against their use in any modern databases. Robert. On Wed, Feb 17, 2010 at 5:22 PM, Adrian Lindberg <[email protected]> wrote: > Only had one, but with 4 high-poly geometries. Again, it wad due to the slow > glBegin glEnd type of drawing flagged by USE_VERTEX_ARRAY (profiler showed > lots of GLBeginEndAdapter). Didn't pick up on it initially because of > readNodeFile gives a different list (either display or VBO). > > But I eventually will have plenty (surely around 30-40). A bit uncertain on > performance there, not all of which will nag the DatabasePager but it still > feels a bit risky. > > ------------------ > Read this topic online here: > http://forum.openscenegraph.org/viewtopic.php?p=24297#24297 > > > > > > _______________________________________________ > 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
