Reply to thread

Message

<blockquote data-quote="edterbak" data-source="post: 709950" data-attributes="member: 69192">The dll which works best for you is (at the moment) up to you to find out. If the stock one doesnt present any glitches or problems, stick with it. You have to test.The way how to read the shift+1 graph: two vertical lines moving from left to right. The way I use this is to see if there is a noticable judder in the movement. Originally you could also see tearing with it. (upperhalf of the screen is different from lower part) But now with W7-AERO taking care of tearing it isnt needed anymore for that purpose. The graph with 2/3 lines green, red and yellow. The ideal situation is if all lines are as flat as can be. This means each image is presented and drawn on time / in sync with the displays refreshrate. If they are out of sync you could see spikes or sloping lines (and up again). In general the latter isnt what you want to see.For me the most important text is the number of frames dropped. Upon pressing play it is possible a number of frames are dropped. With my setup, I sometimes see this number go up to ~40frames. After that, it stays constant for long periods. I.E After playing 50.000 frames I drop 2-5 frames. Ideally those are gone as well. @ Tourrets/Owlsroost: Is this correct what Im writing? Or am I leaving something out?</blockquote>

[QUOTE="edterbak, post: 709950, member: 69192"] The dll which works best for you is (at the moment) up to you to find out. If the stock one doesnt present any glitches or problems, stick with it. You have to test. The way how to read the shift+1 graph: two vertical lines moving from left to right. The way I use this is to see if there is a noticable judder in the movement. Originally you could also see tearing with it. (upperhalf of the screen is different from lower part) But now with W7-AERO taking care of tearing it isnt needed anymore for that purpose. The graph with 2/3 lines green, red and yellow. The ideal situation is if all lines are as flat as can be. This means each image is presented and drawn on time / in sync with the displays refreshrate. If they are out of sync you could see spikes or sloping lines (and up again). In general the latter isnt what you want to see. For me the most important text is the number of frames dropped. Upon pressing play it is possible a number of frames are dropped. With my setup, I sometimes see this number go up to ~40frames. After that, it stays constant for long periods. I.E After playing 50.000 frames I drop 2-5 frames. Ideally those are gone as well. @ Tourrets/Owlsroost: Is this correct what Im writing? Or am I leaving something out? [/QUOTE]

Verification