Hey Andreas thanks for the tip. I'll have to check that out. I have a test
application where the picking would almost always return the wrong object,
never the closest one, and sometimes none at all. I was under the
impression that there was a bug out for it that was being fixed in 1.2.1.
Do you have an example you could post?
Daniel
> -----Original Message-----
> From: Andreas Ebbert [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 04, 2000 12:12 PM
> To: [EMAIL PROTECTED]
> Subject: [JAVA3D] hint: correct picking order requires PickRay
>
>
> Hi,
>
> this just took me some time to find out. Either there is nothing about
> it in the tutorial or the api-documentation or it is somewhere hidden.
> Or I was too blind to see %-)
>
> I had severaly objects overlaying and after I found out that the
> Geometry needs the capability to allow geometry reading and not the
> shape3d (*grin*) I had the problem, that PickTool.pickClosest() did in
> no way pick the closest Shape3D! And what was the solution? Tolerance
> has to be 0.0f :-) If it is not, a PickCone is used instead
> of a PickRay
> and then Shape3D.intersects does not return the distance...
>
> well, maybe someone does find this helpful.
>
> Andreas
>
> ==============================================================
> =============
> To unsubscribe, send email to [EMAIL PROTECTED] and
> include in the body
> of the message "signoff JAVA3D-INTEREST". For general help,
> send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
