Hi,
>Where could I find some sample source of Collision Detection Algorithm with
>picking system?
Current implementation use each Shape3D bounds to
build an hierachical tree. So the default USE_BOUNDS
intersection should be quick. You can also set your
own Collision Bounds instead of Java3D auto compute
bounds.
However, USE_GEOMETRY use a brute-force approach to
detect face-face intersection in the geomery level after their
bounds are collided. So the performance will slow
down. As a result, using a lot of Shape3D for
geometry is faster than packing all the geometry
into a single Shape3D when doing Collision Detection.
>
>I already use the standard behavior, and I use one Java pattern (supervisor)
>notying other objects when a collision is detected so I disable theirs
>behaviors. Anyways the standard collision behavior doesn´t seem very
>accurate.
>
A bug 4419555 is filed for investigation for this inaccurary.
Thanks.
- Kelvin
-------------
Java 3D Team
Sun Microsystems Inc.
===========================================================================
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".