Hello
I noticed that in LineSegmentIntersector::Intersection the function that
returns the local intersection point returns osg::Vec3d, but the local
normal point returns osg::Vec3.
Is there a reason? I'm trying to change my entire application to use double
and Vec3d instead of floats (because of
Hi Roni,
Precision isn't normally required for normals, as they always are of
of unit length without any precisions issues.
Its only position data on large models, such as whole earth, that have
issues with point data and precision, so double precision is required.
Robert.
On Sun, Mar 23, 2008
Hello,
I came back with this problem of first/third view person.
Paul, following is what I did, and it doesn't give me what I was expecting.
So, can you be more precise regarding the inverse of the cow's
transformation?
cViewer = new osgViewer::CompositeViewer();
Hi Robert,
Thanks for clearing that out.
In VPB, is it possible to build levels beyond the highest resolution of
the dem/imagery by extrapolating the data?
--
Rahul Srivastava,
Member of Technical Staff,
Visualization Experts Limited.
www.vizexperts.com
+91-98738-85880 (M)
Robert Osfield
On Sun, Mar 23, 2008 at 6:35 PM, Rahul Srivastava [EMAIL PROTECTED] wrote:
Hi Robert,
Thanks for clearing that out.
In VPB, is it possible to build levels beyond the highest resolution of
the dem/imagery by extrapolating the data?
VPB on creates as many levels as the source data
Hi,
What's the version of OSG and Virual Studio you are running of osgActiveX?
I meet more error while rebuild the project and regsvr32.exe the osgMFCAx.ocx.
could give some help.Thank you.
DonZin 2006.3.24
在2008-03-18,Wang Rui [EMAIL PROTECTED] 写道:
Hello all,
The attached .zip file is a
6 matches
Mail list logo