First, thanks for your input! > I've read somewhere (can't find it back just now) that > WakupOnElapsedTime REALLY may hog the CPU, because J3D then > can't behave event driven, but must poll for the right time > to awake that Behavior.
So Java3D doesn't use OS/hardware timers for this functionality??? Or is the "may" clause in your sentence refect an implementation specific issue? :-) Simeon =========================================================================== 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".
