Hi Ryan, On Tue, Jul 21, 2009 at 4:11 PM, Kawicki, Ryan H<[email protected]> wrote: > I am curious as to what the importance of the node path list is for the > database pager. More importantly, why does the > FindCompileableGLObjectsVisitor need to have a complete path from the > group to be loaded all the way to the root camera node?
It's so the NodeVisitor had be set up with the full parental path so it works as it it came from the root, rather than just the local subgraph. Having the full parent path in the NodeVisitor is used by the osgTerrain::TerrainTile to enable it find it's enclosing osgTerrain::Terrain from the parental node path, the Terrain provide hints to TerrainTechnique that builds the final terrain geometry such as sample density. Without pushing the full parent node path we'd have to delay the compute of the terrain geometry to after the new subgraph had been added into the scene graph - something which would break frame. > It looks not to > serve any importance and there is the possibility that an iterator can > be invalidated on the parent list when ascending to the root. The lines > I am looking at are around 588 of DatabasePager.cpp. Thanks. A line number is no use to me or others with specific information which version of the OSG your are talking about. Please provide this and a small code fragment of the area of concern. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
