Hi J-S, Fred, Simon, This topic has arisen previously on osg-submissions, and my recommendation then was that support for double maths through the intersection code shouldn't be a compile option, but an runtime option, this way the ABI wouldn't change and you could enable it when you needed it. I still believe this is the correct route.
As for whether it'll address that issues Fred is seeing I can't say. Cheers, Robert. On Fri, Dec 4, 2009 at 2:04 PM, Jean-Sébastien Guay <jean-sebastien.g...@cm-labs.com> wrote: > Hi Fred, Simon, > >> I turned all floats into doubles, 0.0f's into 0.0's, all osg::Vec3's into >> osg::Vec3d's... >> I still get the same behavior. > > Simon, why don't you submit your code changes (perhaps with a CMake switch > to change the internal data type used between float and double at compile > time, kind of like OSG_USE_FLOAT_BOUNDINGBOX / > OSG_USE_FLOAT_BOUNDINGSPHERE... I'm sure if this is a common problem people > will be glad to have it in the main OSG code base, only a CMake switch > away... And then it will be easy to compare performance between the two and > perhaps make the double version default if there is little/no performance > difference... > > J-S > -- > ______________________________________________________ > Jean-Sebastien Guay jean-sebastien.g...@cm-labs.com > http://www.cm-labs.com/ > http://whitestar02.webhop.org/ > _______________________________________________ > osg-users mailing list > osg-users@lists.openscenegraph.org > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
