Geoff and Michael, my summary on this subject from the list is now now in the Sutras:
http://trapdoor.surak.com.au/~chris/home/java/j3d/PerformanceSutras.html

Paul Byrne gave some platform analysis results results:
   3.The effect of using WakeupOnElapsedTime(time_step) depends on the VM. That is, the Thread sleep(ms) and Object wait(ms) calls have very different results depending on the platform. On Solaris sleep resolution is 10ms and wait resolution is 10ms but with a minimum of 20ms.
     Another issue is the resolution of the System.currentTimeMillis() call which you might want to use to determine the accuracy of the sleep/wait.  On NT the resolution of the timer is 15ms, on Solaris 1ms.
     [Paul Byrne <[EMAIL PROTECTED]>]
   4.For accurate current time results you may want to look at the javax.media.TimeBase in JMF, again accuracy will vary with platform.
     [Paul Byrne <[EMAIL PROTECTED]>]

Geoff Morris wrote:

Hi:Just had another thought ... I tried this method, and the animation was 'jerky' for me at about 50fps or less.  This may be caused by the inaccuracy of System.currentTimeMillis() on Windows (approx. 50ms) ... You may like to search the archives for this, as there has been discussion about this, and it may explain the 20fps frame rate that you get from the WakeupOnElapsedTime behavior (if you're using Windows).Regards,Geoff.--
                  ,--_|\
                 /  Oz  \
Chris Thorne    :)_.--._/
[EMAIL PROTECTED]     v
 

Reply via email to