Hi Sam,
I try the program under v1.2.1_03 and
didn't found the problem that you mention. The message
CollisionDector2 - Triggering node is of Type :BoundingBox CollisionDetector2 - No
arming bound
used.
CollisionDector - Triggering node is of Type :BoundingBox CollisionDetector - No
arming bound
used.
output correct when there is a collision in geometry (not bounds of geometry)
Let me know if I miss something.
Thanks.
- Kelvin
-----------
Java 3D Team
Sun Microsystems Inc.
>Delivered-To: [EMAIL PROTECTED]
>X-EM-Version: 5, 0, 0, 4
>X-EM-Registration: #01E0520310450300B900
>X-Priority: 3
>MIME-Version: 1.0
>Date: Thu, 27 Sep 2001 08:16:17 -0500
>From: Sam <[EMAIL PROTECTED]>
>Subject: [JAVA3D] help with collision detection
>To: [EMAIL PROTECTED]
>
>Hello,
>
>I am resending this message because my source files did not work last time
>- sorry about that.
>
>I was wondering if there is a bug with the WakeupOnCollisionEntry function
>or not. I found that when you make two Shape3D objects together, both set
>to USE_GEOMETRY , one of the shape (i.e. the Triggering object) would
>actually create its own bounding box and used during the collision
>detection.
>
>I have made some modification to the TickTockCollision example to show what
>is happening when to objects collide - both should use their geometry to
>detect the collision but they don't.
>
>Does anyone know of another way in which I can have two objects collide
>with each other and use only their geometry to detect the collision?
>
>
>Thank You,
>
>
>Sam
>
>
>_____________________________________________
>Free email with personality! Over 200 domains!
>http://www.MyOwnEmail.com
===========================================================================
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".
