Hello, In a project I am working on, I need to use intersectors (PolytopeIntersectors, in particular) with double precision floating point, but with the intersectors provided by OSG (using 3.0.1 here), I get only single precision.
I noticed that osgUtil::PolytopeIntersector already contains code intended to make it use osg::Vec3f or osg::Vec3d depending whether OSG_USE_FLOAT_PLANE is defined or not -- but there are one or two places in which a osg::Vec3 is used -- which ends up as floats. osgUtil::LineSegmentIntersector, on the other hand, uses osg::Vec3 (i.e., floats) everywhere. So, I am ready to change the few bits of osgUtil::PolytopeIntersector still using hardcoded osg::Vec3 and to modify osgUtil::LineSegmentIntersector so that it uses a similar approach (that is, use osg::Vec3f and float if OSG_USE_FLOAT_PLANE is defined, otherwise use osg::Vec3d and double) and send this to osg-submissions. (I did some successful experiments with a fully-double osgUtil::PolytopeIntersector already.) Would this be OK? Am am missing something? Would some different approach be preferable? Do you have any other feedback? Cheers, LMB _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
