As far as I know, several of us have tested this and found it to be a bug on some WinXP systems (it doesn't require a fast CPU, it's just a bug in WinXP). The simplist solution is to test for the return of zero and then knowing your running on a defective WinXP system use the normal Java timer routines. (i.e. your code needs two sets of timer code - one for WinXP and one for all other OS configurations).
- John Wright Starfire Research แอนดรูว์ เดวิสัน (Andr ew Davison) wrote: > > Dear All, > > I've been getting a steady stream of e-mails about > J3DTimer.getValue() not working. The bug has been recorded > as: > > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5016273 > > Has anyone got a solution for this? > > Isn't it just a matter of fixing the few lines of code that > extracts the QueryPerformanceFrequency() value inside getValue(). > > Has anyone tried using J2SE 1.5's System.nanoTime() instead of > J3DTimer? > > - Andrew > > ----------------------------------------------------------------------------- > Dr. Andrew Davison E-mail: [EMAIL PROTECTED] > Dept. of Computer Engineering Fax: +66 74 212895 (then 201 after office hrs) > Prince of Songkla University Tel: +66 74 287 379 > Hat Yai, Songkhla 90112, Thailand > http://fivedots.coe.psu.ac.th/~ad > > =========================================================================== > 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".
