Hi Robert -- I'm redirecting this from osg-submissions to osg-users, as it is now more of a general discussion than a submission.
> PagedLOD's that don't have children ordered from lowest to > height res are invalid, Okay. I didn't know that, and it's surprising, as I'm under the impression that the base class "LOD" doesn't have this restriction. > Having multiple children at the > same range will also break this mechanism. To be clear, you are saying that multiple children at the same range breaks the IntersectionVisitor, but is still valid usage, right? I understand it breaks the code in question, thus my submission. Would you like me to resubmit the fix, addressing only the multiple-children shortcoming, and maintaining the range-ordering assumption? > There isn't any > code to catch erroneous PagedLODs, it's currently assumed > that the user will set things up appropriately. I understand it might be useful to assert ordered children, not sure where this would go. > How were the files generated? I have a client with the multiple-children issue. He has multiple children at the "max res" range but is only able to pick one using the IntersectionVisitor (as the case2.osg file demonstrates). With the fix I submitted, all children at the "max res" range are pickable. The out-of-order test case was hand-generated. This is not an issue for my client, but would be an issue for anyone using PagedLOD as a normal LOD. BTW I note a significant difference between the handling of LOD and PagedLOD by the IntersectionVisitor, is this intentional? -Paul _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
