Has anyone gotten WakeupOnCollisionMovement to work as advertised? What I'm seeing is that if a collision exists then the behavior fires continuously, not just when movement occurs. These observations may have already been reported, but i have specifically confirmed them for WakeupOnCollisionMovement: Trying to set bounds (specifically BoundingSphere) on a triggering object does not work. It does not work for a Node with setBound, with or without auto-compute enabled. It does not work for a Group, either with setBound or setCollisionBound. The value returned by getBound and getCollisionBound reflects the value that was set but the collsion will only work with the target object's auto-computed bounds. Conclusion: Collision is fairly broken. Sun, Will collision be fixed in 1.2? --jon ____________________ Peculiar Technologies ____________________ Jon Barrilleaux 3800 Lake Shore Ave. Purveyors of [EMAIL PROTECTED] Oakland, CA 94610 Alternate Reality 510.444.4370 voc Augmented Simulation 510.444.0231 fax www.augsim.com and 3D Solutions =========================================================================== 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".
