Hello, I have been working with the collision detection portion of Java 3D for the past week. I found that ther are many serious bugs with it. Will if these bugs be fixed in future releases of Java 3D? It will be great if it is the next version :-)
I have come up with a short list of some of the main problems that I think the collision detection package currently have below. 1) The "setCollisionBounds" function seems to work only for Shape3D nodes. For other nodes like TransformGroup, the system tries to look at the children nodes and creates BoundingBoxes for all Shape3D nodes and uses them during a collision. I can't seem to turn this off. 2) The "setAlternateCollision" function does not work properly because it always creates its only BoundingSphere and uses it for collision detection. You cannot replace this sphere with your own bounding shape. 3) The WakeupOnCollisionEntry and Exit behaviors does not seem to be working with the USE_GEOMETRY option because the Triggering object always creates it own bounding box and uses it during a collision Please let me know If you have suggestions for any of the above problems. Thanks for your time, 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".
