Also - shouldn't it be ElapsedFrames(0) to wakeup on the next frame? Wouldn't ElapsedFrames(1) wakeup every other frame?
Lewis. -----Original Message----- From: Discussion list for Java 3D API [mailto:[EMAIL PROTECTED] On Behalf Of John Wright Sent: 25 August 2003 15:26 To: [EMAIL PROTECTED] Subject: Re: [JAVA3D] Thread vs Behavior Ralf, In using the behavior you are tying yourself to the frame rate your machine is able to achieve. With a thread you might slow down rendering (by keeping the machine busy in your thread) but your thread could process potentially thousands of times per frame. - John Wright Starfire Research Ralf Bednarz wrote: > > hello > > Why is a behavior that wakes up every frame and do some setTransform() > slower than a thread that does almost the same? I read information of > a transfrom3d and want to update the positon of an object in my scene. > But when I use abehavior that wakes up on ElapsedFrame(1) my whole > application gets slow as snails. Does a thread do that thing it is > quite good. > > Has the Behavior class much overhead that it almost crashes in doing > this stuff? > > thanks > Ralf > > ====================================================================== > ===== > 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". ======================================================================== === 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". =========================================================================== 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".
