multimedia timers worked great. I got down to 5ms which is way faster than I need.

So much for it being labelled as obselete.

03-09-2010

VirtualAce

QueryPerformanceCounter()
QueryPerformanceFrequency()

03-10-2010

GReaper

Quote:

Originally Posted by Bubba

QueryPerformanceCounter()
QueryPerformanceFrequency()

Remember that those only work with LARGE_INTEGER ( or whatever its name is ).

03-11-2010

VirtualAce

Why are you telling me? I use those everyday.

timeGetTime() stinks for high res timing.

03-12-2010

GReaper

Quote:

Originally Posted by Bubba

Why are you telling me? I use those everyday.

timeGetTime() stinks for high res timing.

So, what are you telling me?
High res timing is more accurate with LARGE_INTEGER(long long)
(Those two functions take LARGE_INTEGER as argument!)

03-12-2010

Mario F.

Quote:

Originally Posted by Sipher

So, what are you telling me?
High res timing is more accurate with LARGE_INTEGER(long long)
(Those two functions take LARGE_INTEGER as argument!)

*sigh*

It has nothing to do with it being a LARGE_INTEGER. The accuracy is determined by your system. On older systems, you will in fact have less accuracy since it will use the PCI bridge timers and these may jump time ahead by a few seconds due to a bug. On other systems that have SpeedStep enabled you will also have less accuracy since the processor frequency will fluctuate, despite the function being the same on all cases.

What determines the accuracy of this method is your processor frequency, your operating system support, the type of processor being used and whether or not it supports SpeedStep and has it enabled. The argument type is just a consequence of how the function works (and what it reads).

03-12-2010

GReaper

Well, ok, i didn't know that!

03-12-2010

VirtualAce

Quote:

So, what are you telling me?
High res timing is more accurate with LARGE_INTEGER(long long)
(Those two functions take LARGE_INTEGER as argument!)

I'm telling you the answer. What you do with it is your business. Research it. The SDK provides all types of information about the various timers in Win32. Use the timer that best suits your needs. I have had no luck with allowing the API to time things for me and give me callbacks or whatever when its done. Way too slow and cumbersome. I love how I give you one answer and you proceed to tell me how my answer functions when I would think it to be apparent I know how the function works since...um....I suggested you use it.