John Wright wrote: > 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).
This is not the impression given by the bug report. Perhaps you could add your opinion at the end of: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5016273 In the j3d-interest list, you're the only person to have mentioned the bug previously. > 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). Yes. What timer alternative did you use? But what about uses of J3DTimer inside other parts of Java 3D? For example, J3DTimer is used by the SensorEventAgent class in the Java 3D utilities. Since the timer usage is 'hidden', it may be too difficult to substitute in another timer. Has anyone experience of this problem? --- My own guess is that System.nanoTime() and J3DTimer are implemented on Windows in exactly the same way. So does nanoTime() fail when J3DTimer fails? - Andrew =========================================================================== 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".
