|
Custom Resolution Utility (CRU)
|
|
07-15-2016, 05:25 PM
(Last edited: 07-15-2016, 05:31 PM by RealNC)
Post: #2149
|
|||
|
|||
|
RE: Custom Resolution Utility (CRU)
Hello Toasty!
I found a strange issue with CRU (1.2.6) and the timings it produces. I'm using a monitor that goes up to 77Hz (it's an old Samsung XL2370). Setting up a 1920x1080 77Hz mode in the nvidia control panel works perfectly when using reduced timings. The monitor OSD shows 77Hz and indeed an FPS counter with vsync on shows 77FPS. So I know it's working. However, the modes created in the nvidia panel are not always recognized by games. Even worse, those modes don't work if I enable DSR (4K downscaling). CRU to the rescue. But setting 1920x1080 77Hz and reduced timings results in a black screen and the monitor OSD pops up, saying it doesn't recognize the input signal. So the CRU-generated timings are different than the nvidia ones, which do work fine! If I use 1920x1080 76Hz with reduced timings, that works. But I'd like to get that "last lousy Hz" out of it ;-) Is there a way I can use the exact same timings as generated by the nvidia panel (which work fine) and import them into CRU, so that I can get a working 77Hz mode set as a primary mode? |
|||
|
|
« Next Oldest | Next Newest »
|