Hi John, On 10 June 2013 23:55, PCJohn <[email protected]> wrote: > Hi Robert, just quick answer (as I found an internet place on my holiday > trip...)
!! You should be out enjoying sun rays not thinking about virtual rays ;-) > - starting point as Vec3d - not a problem for me > > - direction (vec3d) instead of end point (vec4d) - at the end.... it is not a > problem for me. I started to think whether it would not give us trouble to > switch LineSegmentIntersector by RayIntersector in OSG code. Two cases, I > considered: > During IntersectionVisitor::apply: LineSegmentIntersector is transformed by > MatrixTransform and should be RayIntersector afterwards (as MatrixTransform > contained special matrix). I don't think one can simple transform a LineSegmentIntersector based traversal into a RayIntersector one, the Intersection hit class will be different and incompatible. If one wants to handle novel transforms/projections then it will be best to start with a RayIntersector. > Second case, osgViewer::View::computeIntersections would need to consider > which intersector it should use. But this should, hopefully, be simple, > although I am not sure before implementing it. We'd probably just need two versions of computeIntersections. Robert. _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
