Reply to thread

Message

<blockquote data-quote="tourettes" data-source="post: 608407" data-attributes="member: 10858"><p>Owlsroost, any good ideas how to replace the display cycle detection code with something working? <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /> That current way is much too inaccurate (and cannot be used in at any MP release as such).&nbsp; After all, over a 10% deviation is simply just too much (23.xxx ms vs. 20.000ms). Error should be less than 0.5% to be acceptable. For Windows 7 we already have OS based API to tell, but XP and Vista users are left in cold. Maybe James could tell how ReClock does it (it has a setting for DirectX / DirectDraw, but I'm not sure what API calls it is using... and too lazy to try to spy those with anything <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />)</p></blockquote><p></p>

[QUOTE="tourettes, post: 608407, member: 10858"] Owlsroost, any good ideas how to replace the display cycle detection code with something working? :) That current way is much too inaccurate (and cannot be used in at any MP release as such). After all, over a 10% deviation is simply just too much (23.xxx ms vs. 20.000ms). Error should be less than 0.5% to be acceptable. For Windows 7 we already have OS based API to tell, but XP and Vista users are left in cold. Maybe James could tell how ReClock does it (it has a setting for DirectX / DirectDraw, but I'm not sure what API calls it is using... and too lazy to try to spy those with anything :)) [/QUOTE]

Verification