> > BTW I note a significant difference between the handling of LOD and > > PagedLOD by the IntersectionVisitor, is this intentional? > > Well PagedLOD has the fallback mechanism, and has strict > ordering constraint that's what makes it different.
Switch derives from Group, and if I create a Switch and set all its children on, I think we can all agree that it should act just like Group. In the same way, since PagedLOD derives from LOD, once all its children are loaded, I'd expect it to work just like LOD. But this isn't what I see. Attached are two files, identical except that one uses an LOD and the other uses a PagedLOD. Run osgpick on both, and you'll see that it works fine for the PagedLOD case, but fails to pick anything for the LOD case. I suspect the problem is in how IntersectionVisitor has completely different logic for both LOD and PagedLOD, but without understanding the difference, I'm not inclined to tinker with the code. What do you make of it? Is the LOD test case just a badly-formed LOD because the max range doesn't go to zero distance? If so, again, this is a restriction of LOD usage that I'm not aware of, nor do I understand why it isn't also a restriction on PagedLOD usage... -Paul
paged.osg
Description: Binary data
lod.osg
Description: Binary data
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
