High precision timer - GameCreators Forum

Author

Message

Cryptoman

20

Years of Service

User Offline

Joined: 24th Nov 2003

Location: Utah Mountains

Posted: 25th Jan 2005 10:43 Edited at: 25th Jan 2005 14:00

Link

Well I know some of you are unhappy with the current timer function so here is one that is 6 more digits. It calls your cpu timer directly. Unlike the kernel ticker which which is in 1ms increments(supposed to be) and only gets updated whenever the OS feels like it, the cpu never stops ticking.

+ Code Snippet

load dll "kernel32.dll",1
a as   dword
b as   dword
time as  double float
d as dword
make memblock 1,8
for x=0 to 7
write memblock byte 1,x,0
next x
c=get memblock ptr(1)
a=call dll (1, "QueryPerformanceFrequency",c)
b=*c


do
   time2=timer()
      a=call dll (1, "QueryPerformanceCounter",c)
      d=*c

         wait 1000
         a=call dll (1, "QueryPerformanceCounter",c)

            a=*c
         Time = ((a-d)*1000.000000)/b
         time2=timer()-time2
      set cursor 0,0
   cls
   Print time;" ";time2
loop

Back to top

Profile PM

Mason

20

Years of Service

User Offline

Joined: 20th Mar 2004

Location: Arizona

Posted: 25th Jan 2005 11:18 Edited at: 25th Jan 2005 11:18

Link

Hmm, didn't seem to work properly. I used it in Dark Basic Pro if that matters. Its 8:17 pm here and it is giving me

-1530.999 1001

I'm not exactly what happened there. Good Idea Though.

¤§Mason§¤

http://www.geocities.com/blacklab_studios

Back to top

Profile PM Email Website

Cryptoman

20

Years of Service

User Offline

Joined: 24th Nov 2003

Location: Utah Mountains

Posted: 25th Jan 2005 11:26

Link

Ah, you must be using a pentium? No? My goof for posting without testing different cpu's. I have amd 2600. Let me see if it can be self adjusting.

Back to top

Profile PM

Cryptoman

20

Years of Service

User Offline

Joined: 24th Nov 2003

Location: Utah Mountains

Posted: 25th Jan 2005 11:51

Link

I changed the code so that the frequency is unsigned and tested it on my pentium 800 mhz. The difference in time should now represent true time compared to kernel ticks. Kernel ticks are not accurate. Depending on what the OS is doing it may or maynot be updated correctly. I've gotten a 500ms difference on XP before. Am hoping nobodys counter runs faster than what a dword can hold.

Back to top

Profile PM

Sorry your browser is not supported!

Code Snippets / High precision timer