> >I'm trying to implement the VisibilitySensor for VRML. This time(take 3 >for the J3D list as a whole at least), I'm using a >WakeupOnCollisonEntry. I'm creating a geometry representing the viewing >frustum. All is well and good as long as I use a Shape with a real >geometry node. But the moment I just use the bounds things stop >working. Using the rendering attributes setVisibile to false works as well. > >So my question is this. If you have a shape without a geometry, but >you've called setCollisionBounds on it(and setCollidable) is it eligable >for collison for a USE_BOUNDS case? My read of the documentation makes >me think so, but I'm not sure.
Yes, this should be the case. You may have found a bug. > >Another point here. I'm using > wocen = new WakeupOnCollisionEntry(bounds); > >The documentation doesn't explicty state that this is using a speedHint >of USE_BOUNDS? But I assume it is as there is no method to >setSpeedHint, and well I've only passed in a BOUNDS. Any constructor that doesn't have a speed hint defaults to USE_BOUNDS. Doug Twilleager Java 3D Team Sun Microsystems =========================================================================== 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".
