Reply to thread

Message

<blockquote data-quote="Owlsroost" data-source="post: 609453" data-attributes="member: 83973">Thanks Jong and Tourettes for all the interesting discussion points and info <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />For reference, all my dll versions to date perform 'sync to nearest display vsync' correction for 2:1 and 1:1 FPS ratio situations, and the v003 &amp; v004 versions do it for all FPS ratios (it's never disabled).Meanwhile, the 'bursts of judder' investigatons are continuing - and no, it doesn't seem to be presentation/vsync positioning judder, the 'paint' position relative to vsync is the same in all cases. What seems to be happening is that it paints two frames then skips one (repetitively), resulting in a juddery 33.3333 fps with no dropped frames reported. This is at 50Hz with 1:1 fps ratio.Tony</blockquote>

[QUOTE="Owlsroost, post: 609453, member: 83973"] Thanks Jong and Tourettes for all the interesting discussion points and info :) For reference, all my dll versions to date perform 'sync to nearest display vsync' correction for 2:1 and 1:1 FPS ratio situations, and the v003 & v004 versions do it for all FPS ratios (it's never disabled). Meanwhile, the 'bursts of judder' investigatons are continuing - and no, it doesn't seem to be presentation/vsync positioning judder, the 'paint' position relative to vsync is the same in all cases. What seems to be happening is that it paints two frames then skips one (repetitively), resulting in a juddery 33.3333 fps with no dropped frames reported. This is at 50Hz with 1:1 fps ratio. Tony [/QUOTE]

Verification