Custom Resolution Utility (CRU)

[noyaux]

Hello guys, to begin with, this tool is awesome I created a custom resolution : 1440 1080 on my 24" Benq monitor but I have some questions.
Do this will create additionnal input lag? as I do compete in cs go I would like to know that. Plus, I created manually the timing using the same values as the default mode which was in 1920 1024 and just changed the resolution to 1440 1080 and refresh rates to 144 Hz (my monitor capable Hz)
but for the timings I don't know if it gives me a disavantage or not as I see LCD reduced timings which have really different values that I have. I don't understand what these values do but I would like to know if default are better or LCD reduced for input lag and such . I linked my CR you can see the timings there.
For my testing I've tested using vsync it correctly sync at 144 fps in my game
and I used a map which could test your reaction time and it was quite good like before but I want to be sure
should I use standard or reduced lcd mode with my benq 2411t?
Cordially.

[terencewklau]

Does cru.exe have command line options so that the settings can be scripted? I tried cru.exe /? but did not get any help options that could point me in the right direction.

Thanks.

[ToastyX]

(09-24-2014 03:57 AM)terencewklau Wrote:  Does cru.exe have command line options so that the settings can be scripted?

No.

[ToastyX]

(09-18-2014 10:59 AM)noyaux Wrote:  Hello guys, to begin with, this tool is awesome I created a custom resolution : 1440 1080 on my 24" Benq monitor but I have some questions.
Do this will create additionnal input lag? as I do compete in cs go I would like to know that.

It depends on the monitor, but with most monitors, no. If the monitor did add lag with lower resolutions, you could use GPU scaling instead.

(09-18-2014 10:59 AM)noyaux Wrote:  Plus, I created manually the timing using the same values as the default mode which was in 1920 1024 and just changed the resolution to 1440 1080 and refresh rates to 144 Hz (my monitor capable Hz)
but for the timings I don't know if it gives me a disavantage or not as I see LCD reduced timings which have really different values that I have. I don't understand what these values do but I would like to know if default are better or LCD reduced for input lag and such . I linked my CR you can see the timings there.
For my testing I've tested using vsync it correctly sync at 144 fps in my game
and I used a map which could test your reaction time and it was quite good like before but I want to be sure
should I use standard or reduced lcd mode with my benq 2411t?

The "LCD reduced" option was meant for trying higher refresh rates at the native resolution. I would use "LCD standard" if that works. The values won't have a significant impact on lag. In theory, the refresh will finish slightly faster with a higher vertical blanking/total, but we're talking less than 1 ms in most cases because most monitors won't accept a high enough value to make a significant difference.

[noyaux]

Thanks for the answer ToastyX =) this tool is extremely useful, I put a better resolution on one of my low end PC and gaming is much much better with it now.

[hexafluoride]

Great utility! One problem though, it doesn't accept zero values for the blanking fields. I can do this with PowerStrip, so why doesn't CRU support it?

Also, for some reason, even though I patched my driver for >165MHz pixel clocks, my monitor seems to display "out of range" after 165MHz. Why does this happen? Monitor(ViewSonic VA-2248LED) input is DVI-DL, card(ATi Radeon HD 5670) output is DVI-DL, cable is DVI-DL.

Keep up the good work!

[MS-DOS]

(09-28-2014 04:20 PM)hexafluoride Wrote:  Also, for some reason, even though I patched my driver for >165MHz pixel clocks, my monitor seems to display "out of range" after 165MHz. Why does this happen?

Monitor's hardware\firmware limit. I have the same on my DELL U2212HM and had it on my previous U2211H on both DVI and DisplayPort.

[ToastyX]

(09-28-2014 04:20 PM)hexafluoride Wrote:  Great utility! One problem though, it doesn't accept zero values for the blanking fields. I can do this with PowerStrip, so why doesn't CRU support it?

The driver won't accept zero values even though it's technically possible. PowerStrip bypasses the driver and communicates with the video card directly, which is why it has limited compatibility with newer video cards.

(09-28-2014 04:20 PM)hexafluoride Wrote:  Also, for some reason, even though I patched my driver for >165MHz pixel clocks, my monitor seems to display "out of range" after 165MHz. Why does this happen? Monitor(ViewSonic VA-2248LED) input is DVI-DL, card(ATi Radeon HD 5670) output is DVI-DL, cable is DVI-DL.

"Out of range" usually indicates a monitor limitation. If 165.00 works but 165.01 doesn't, then there might be another driver limit.

[MS-DOS]

(09-30-2014 12:14 PM)ToastyX Wrote:  If 165.00 works but 165.01 doesn't, then there might be another driver limit.

If so, then it applies to DisplayPort too, and that's kinda weird.

[HesAlwaysNearus]

Hello there. I registered here becouse i have question about CRU. Im using Iiyama PRO 454 19" CRT monitor. Program lets me to use 85/100 hz refresh rate on Windows 7. testufo shows true refresh rates and everything is fine (it shows 85 or 100 hz). But when im starting any game the monitor is switching (something like turn off and then asap on) and the refresh rates drop to 60 hz.
What should i do to get same 85/100 hz in games?
Sorry for my english languages skills