Original Post
Hi, Up until now, I was using the "rdtsc" instruction to measure my time-delta's. Now my colleague got a dualcore machine and it's giving problems because the delta-t's are very irregular (app runs 'skipping' frames). If you set the app to run only on cpu 1, then the problems immediately disappears. I found two solutions for the problem: 1 Run a thread with a Sleep (1), an realtime priority, with a threadAffinityMask to a certain processor, and update a 'currentTime' value (eg with rdtsc). Running on normal priority doesn't work correctly 2. Use the Time timeGetTime() (only 1 ms accuracy) I'm not really fond of the thread-idea, looks like overkill just to get a simple time - and I'm not sure I like the winmm.lib I need, just for the timeGetTime function. So is it possible to do whatever timeGetTime does myself? What does this function do that avoids the multi-cpu timing problems? Does spawn a thread - like I did - and thus limit the accuracy to 1 ms? Is it at all impossible to use the rdtsc instruction on dualcore machines? Thanks in Advance, Roger