Peter Hrenka wrote: > If you can split up your point cloud into multiple Geodes > you should already see a speedup with PolytopeIntersector > as it can take advantage of available bounding volume > information. Well, in order to do that I would have to sort the points into some kind of reasonable bounding hierarchy. My application works with point scan data collected by a high resolution laser scanner and includes a surface reconstruction mesh, so to split up the data set would also require duplicating points to avoid creating seams in the mesh. Not insurmountable, but more work. Also in my application usually the entire data set is visible, so there are no culling/rendering benefits to splitting up the data (unless it is faster for some reason to have 'n' vertex buffers of size 'm' instead of one 'n*m' VBO?) > > Still, I'd also like to see Kd-Tree support for PolytopeIntersector. > I do not have much time to do this myself but I could offer some > hints and perform testing if you choose to implement it. Ok, I will take a look at it.
-- Peter Amstutz Senior Software Engineer Technology Solutions Experts Natick, MA 02131 _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
