Hi Terry, The osgdem/osgTerrain generated databases might be a good guide for you, the way they ensure that no holes appear is to always have the first child of PagedLOD as local subgraph that isn't loaded from a file reference, this first child is the lowest level of detail level and acts as a fallback for when no other children are available.
The next child in each PagedLOD is then the external tile that replaces these lowest level of detail child with one that is loaded from disk, this file contains a Group containing four PagedLOD nodes, and each of these PagedLOD nodes has its first child defined as local geometry/texture as per the above, and its second child the external file reference. This recurses until you get to the highest level of detail. Robert. On 12/27/06, Terry Welsh <[EMAIL PROTECTED]> wrote:
I'm still stumped on this problem. Does OSG have a mechanism for ensuring that the children PagedLODs of a parent PagedLOD have all loaded their content before the parent content is switched off and the childrens' content is switched on? Without that, I am seeing temporary holes in my terrain while I wait for tiles to load. I tried running my scenegraph with osgsimplepager, but that doesn't help. I believe it just manages PagedLOD loading on a separate thread, but I can't find any documentation on DatabasePager. - Terry _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
