"Yes, RTFM on timeBeginPeriod and timeEndPeriod."

I had actually already tried timeBeginePeriod, and the although there was nothing specific for XP in the manual. The manual did mention that Window2000/NT was likley to be set at 5 milliseconds. Looks like the problem with timeGetTime() was actually a loss of significance as a result of using floating point rather than double or DWORD.

Using timeGetTime does seem to fix the Jerky motion, it just is to bad that the performace counter does not seem to work; as the Microsoft MVP site actually does not recommend timeGetTime() in a tight loop.

For the record, my chipset is only a partial register match for the performance counter issue. Although, Microsoft does say that there is more chipsets to identify.

Thanks, CrazedGenius
Thanks, IndirectX; for the record I do read the manual.


[edited by - sdoherty55 on June 23, 2002 6:35:19 PM]

quote:Original post by sdoherty55
Big Sassy,

Are you using D3DAPP.C for your performance timer or did you implement your own? Although, I don''t think that their should be a difference given it D3DAPP.C AND DXUTIL.C are using the QueryPerformanceCounter.

I use my own that uses QueryPerformanceCounter. IndirectX, that article sounds like that''s exactly what my problem is. I''m going to test it out in a sec and see if there is any difference. In any case, thanks for pointing out that article.

***********************
          

didn''t read all the posts, but maybe this could help..
http://www.mvps.org/directx/articles/implementing_steady_motion.htm

IndirectX, I didn''t see your post until today. I will try your test program tonight and let you know.

Thanks for the Help.

AP, I actually already had the printouts from the Microsoft MVP site on you desk. That is a good site, full of information.