On Sun, 4 Mar 2001, David wrote:
> looks like at around 50 fps, I am getting 3 dups for every 1 real frame
> recalc. Course everything still looks right, but I am losing 3 steps of
> smoothness.
> At 50 fps, I am calculating a frame every 20 ms. I thought the
> System.currentTimeMillis() had a resolution of 5ms, but it looks like I am
Thanks to whoever, currentTimeMillis uses the windows timer which
is only accurate to 18.<something> ms. Thus your numbers.
I wrote my own JNI function to get a good timer. I think it was
very negligent for whoever not to make currentTimeMillis as close to 1ms
accuracy as possible on all systems.
> dead wrong. The numbers below look like 60ms, but its probably 50ms. How
> can I get the time to a better resolution?
--
Marc Hernandez
!speakingFor(WildTangent);
===========================================================================
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".
