I just found the following paper: http://algo2.iti.kit.edu/wassenberg/timing/timing_pitfalls.pdfIf I get it right, there is a reliable timer called High-Precision Event Timer (HPET) on current hardware and QPC uses that from Vista on.
The following operating systems are known not to be able to use HPET: Windows XP,[note 2] Windows Server 2003, and earlier Windows versions, Linux kernels prior to 2.6.[note 3]The following operating systems are known to be able to use HPET: Windows Vista, Windows 2008, Windows 7, x86 based versions of Mac OS X, Linux operating systems using the 2.6 kernel, FreeBSD and OpenSolaris.
Before we can implement a workaround, we need a reliable way of determining if a timer is "wrong" ... ?
ok changes made.If you have any other remarks do point them out, always trying to make it better
General: Added support for disabling runtime function checks, buffer checks and state tracking. Activated with -Dorg.lwjgl.util.NoChecks=true
Notice: We'd like to remind people to include the copyright, conditions and disclaimer statement for LWJGL in their products, as required by the license. Though we are not about to claim foul in any way, it would be nice to see a link back to lwjgl.org in the credits or documentation at the very minimum.
Hi, Again a great release! Quote from: Matzon on July 16, 2010, 11:20:05General: Added support for disabling runtime function checks, buffer checks and state tracking. Activated with -Dorg.lwjgl.util.NoChecks=trueI've dreamt of this point since a long time.
Quote from: wondersonic on August 09, 2010, 18:29:04Hi, Again a great release! Quote from: Matzon on July 16, 2010, 11:20:05General: Added support for disabling runtime function checks, buffer checks and state tracking. Activated with -Dorg.lwjgl.util.NoChecks=trueI've dreamt of this point since a long time.Yeah, me too. I tried disabling the checks but found it made no difference... Could you measure the performance impact of the runtime checks?