On Aug 15, 2005, at 1:53 PM, Joseph Nastasi wrote:
Assume they are okay. The Model is at 0,0,0 with a Radius of 20.22.
Planet.Position is at 0,-637989,0 and has a radius of 607813. Given
this, it doesn't seem like the Intersect should have returned True.
There should be 30156 of space between the two.
I agree. Can you reproduce this in a simple app -- create bounds1,
create bounds2, show that they intersect when they shouldn't?
Done and attached to this report:
http://www.realsoftware.com/feedback/viewreport.php?reportid=aefpnfic
Note that there are two issues. The intersect fails when it should not
the first time. The second issues is that the radius I assign using New
Bounds3D(New Vector3D, 63000) is changed when UpdateBounds is called;
setting to the value that was calculated when ComputeBounds was used
instead of New Bounds3D. So it seems that UpdateBounds (whether called
or when objects in question are rendered) does not respect the assigned
values.
Thanks
Joe
--
Joseph Nastasi
Pyramid Design - a software development firm
http://www.pyramiddesign.us
Voice 609 601-0814 Fax 609 601-0815
Products:
A-OK! Spacecraft Simulation System - http://aok.pyramiddesign.us
A-OK! The Wings of Mercury
FTP Suite for REALbasic - http://ftpsuite.pyramiddesign.us
Proud Sponsors of REALbasic Olympics 2005
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|