59Hz

hethoofd said:

I'm having the exact same thing (different video card, though). I don't really care about the 1Hz, but it is quite odd...

I am also seeing this on my box, upon a fresh install BEFORE installing the beta NV drivers. Sure can't tell if it has much effect, unless it HELPS, because my video performance is better under 7, especially when viewing my AVCHD home movies in WMP12. Phenomenal!

johngalt said:

Starting next year *I'll* be 39 perpetually too....

I've been 39 for more years than I care to admit, publicly anyway.

Force DVI/HDMI resolutions and refresh rates

Deanos said:

Anybody managed to find any possible solutions to this yet????

Yes. This will help you. You'll need to modify your monitor timings or use a VESA standard timing. Post back here if you need help.

Deanos said:

Thanks, I'll give it a try tonight!

Sounds all very complicated though!

Will this issue be resolved in future releases?

Perhaps future releases of your DISPLAY. That's where the issue comes from. The EDID in your monitor is asking for 59Hz and Windows is giving it what it asked for. This method is a bit complicated because we're compensating for your hardware manufacturer's lack of foresight.

If it's my monitor asking for 59hz, how come everything is 60hz in all my other boots - XP and Vista?

I think it's a a glitch in Windows 7 itself.

Ex_Brit said:

If it's my monitor asking for 59hz, how come everything is 60hz in all my other boots - XP and Vista?

I think it's a a glitch in Windows 7 itself.

Windows 7 uses the exact NTSC timing: (Hz*1000)/1001 so what used to be 60Hz comes out as 59.94 and VESA GTF rules explicitly state that you ROUND DOWN if your application handles only integer values. That being said, we ARE just compensating for this by adding a fudge factor to the timing to get it to round out to 60 again and it will have no effect on performance.

baarod said:

Windows 7 uses the exact NTSC timing: (Hz*1000)/1001 so what used to be 60Hz comes out as 59.94 and VESA GTF rules explicitly state that you ROUND DOWN if your application handles only integer values. That being said, we ARE just compensating for this by adding a fudge factor to the timing to get it to round out to 60 again and it will have no effect on performance.

Well in that case why are we even discussing the issue, as it really is a non-issue, if I read you correctly?