View Single Post
Old 28th March 2018, 19:48   #49914  |  Link
FDisk80
Registered User
 
Join Date: Mar 2005
Location: Israel
Posts: 162
Quote:
Originally Posted by mclingo View Post
have you tried tweaking the timings at all by a single digit, I was doing that with my 1050 to try and maximise the frame drop internal, I say that as some of the timings gave this error suggesting they were out of scope, you might find one thats close enough to use in the meantime.
Yes, I also found out that in all those latest broken drivers setting the custom resolution to 1920x1079 instead of 1920x1080 for example does let you create, tweak all other timings and apply that custom resolution in nvidia control panel.

But doing this makes the picture a little bit strange, it is a bit blurrier because the resolution is no longer a native one.

Also even with 1920x1079 madVR cannot switch to this mode because when trying to set madVR to 1079p24 when it goes full screen it will mark this setup as invalid and does not let you apply this mode. So it just defaults to 1080p24 with non of the settings applied even if you keep the 1920x1079 mode set up in nvidia control panel.

So it looks like nvidia did something that locks the native 1920x1080 resolution so it is no longer possible to tweak unless you also change to non native / non standard resolution.

Last edited by FDisk80; 28th March 2018 at 19:53.
FDisk80 is offline   Reply With Quote