Hi Shayne, The base osgUtil::Intersector class supports setting the limits on intersection results, using the setIntersectionLimit() method. The current options are NO_LIMIT, LIMIT_ONE_PER_DRAWABLE, LIMIT_ONE, LIMIT_NEAREST.
On Tue, Sep 11, 2012 at 9:47 AM, Tueller, Shayne R Civ USAF AFMC 519 SMXS/MXDEC <[email protected]> wrote: > > **1) **Does it support a feature of detecting a “hit” and then > returning without the need to compute all the intersections? This would be > sort of like a visibility test. > Set the intersection limit to LIMIT_ONE > **** > > **2) **Does it have the ability to find the closest intersection > without the need to compute all the intersections? In other words, does it > step along from the starting point of the line segment until an > intersection is found and then bail out? > Set the intersection limit to LIMIT_NEAREST. This mode could be optimized more, but it will currently reject a subgraph if the nearest point of the bounding sphere is further than the nearest hit. So it can still provide significant savings in computation time. Cheers, Farshid > **** > > **3) **If it doesn’t support these features, is it possible to > modify the LineSegmentIntersector to support these?**** > > ** ** > > I would think that having this capability would improve performance where > applicable.**** > > ** ** > > Thanks for any input in advance…**** > > ** ** > > -Shayne**** > > ** ** > > ** ** > > _______________________________________________ > 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
