Hello,
I've been trying to configure blur reduction for playing CSGO, however it is far too dark. I've tried the 1350 trick (http://i.imgur.com/e7KHoUL.png - http://i.imgur.com/2DI9CAP.png) however on the monitor OSD it shows my current resolution as "1920X1080@144". From what i've read that means CRU did not work properly as it should show "@60". As you can see in the screenshot it shows it has saved and is supposedly working correctly. I've tried using the Clock patcher and DDC/CI is enabled. My GPU is a 6950 and the drivers are the latest.
I'd appreciate any help.
Thanks.
XL2411Z CRU VT problems.
-
Falkentyne
- Posts: 2805
- Joined: 26 Mar 2014, 07:23
Re: XL2411Z CRU VT problems.
If it says 144 hz, it means you're running your desktop at 144 hz. VT tweaks do not work at 144 hz.
You need to change to 120hz. However if you did change to 120hz and the OSD is showing 144 hz, that means either the *pixel clock patcher* didn't work at all, and the driver is ignoring 120hz because the pixel clock exceeds 330 MHz (so you need to repatch correctly), or you removed all of the default resolutions (where is 60hz?), however on AMD cards, the default resolutions should still be there unless you also removed all of the standard resolutions as well.
Run the pixel clock patcher again. There were other people who posted, and we found out that they didn't actually patch the values at all.
It should say "values found", and "patch?"
If it says 'already patched, restore from backup?' then try running the driver restarter from the CRU page. It's on the CRU monitortests forum. (or just reboot).
Also add 60hz 1920x1080 back in. There's no reason to remove it (the only reason you would remove it is if you are trying to remove -all- established, standard and detailed resolutions and the extension block and then adding new detailed resolutions and forcing the driver to use --only--the detailed resolutions you entered and nothing else--easiest example is for forcing games that ALWAYS use 60hz refresh rate (or 50hz), to run at 100 or 120hz instead (e.g. Street fighter 4, Crysis, Dark Souls (can or will cause crashes), etc).
If you feel you messed up, you can always run reset-all.exe then run restart64.exe to restart the driver and reset the display to default.
You need to change to 120hz. However if you did change to 120hz and the OSD is showing 144 hz, that means either the *pixel clock patcher* didn't work at all, and the driver is ignoring 120hz because the pixel clock exceeds 330 MHz (so you need to repatch correctly), or you removed all of the default resolutions (where is 60hz?), however on AMD cards, the default resolutions should still be there unless you also removed all of the standard resolutions as well.
Run the pixel clock patcher again. There were other people who posted, and we found out that they didn't actually patch the values at all.
It should say "values found", and "patch?"
If it says 'already patched, restore from backup?' then try running the driver restarter from the CRU page. It's on the CRU monitortests forum. (or just reboot).
Also add 60hz 1920x1080 back in. There's no reason to remove it (the only reason you would remove it is if you are trying to remove -all- established, standard and detailed resolutions and the extension block and then adding new detailed resolutions and forcing the driver to use --only--the detailed resolutions you entered and nothing else--easiest example is for forcing games that ALWAYS use 60hz refresh rate (or 50hz), to run at 100 or 120hz instead (e.g. Street fighter 4, Crysis, Dark Souls (can or will cause crashes), etc).
If you feel you messed up, you can always run reset-all.exe then run restart64.exe to restart the driver and reset the display to default.
-
saigoNcsgo
- Posts: 2
- Joined: 21 Dec 2014, 19:35
Re: XL2411Z CRU VT problems.
Thank you very much for your detailed reply.
I changed my desktop to 120hz and that seemed to do the trick, on my OSD it shows 1920x1080@60 (This means it is working correctly from what I understand) and it also looks brighter. I also did as you said with the patcher and CRU and that worked all fine. I appreciate your help, you did the trick!
Thank you.
edit - The 1502 tweak also works at 120hz and 1920x1080, correct? According to CRU it's working correctly.
I changed my desktop to 120hz and that seemed to do the trick, on my OSD it shows 1920x1080@60 (This means it is working correctly from what I understand) and it also looks brighter. I also did as you said with the patcher and CRU and that worked all fine. I appreciate your help, you did the trick!
Thank you.
edit - The 1502 tweak also works at 120hz and 1920x1080, correct? According to CRU it's working correctly.
-
Falkentyne
- Posts: 2805
- Joined: 26 Mar 2014, 07:23
Re: XL2411Z CRU VT problems.
Yep, the screen got brighter because with the VT Tweaks, the monitor is using the 60hz backlight pulses instead of the default 120hz ones. (you can see the persistence values for the default (non VT) refresh rates at http://display-corner.epfl.ch/index.php/BenQ_XL2411Z
You can tell from the 120hz listing (with some easy math), that 1.0ms persistence=strobe duty 012, WITHOUT a VT tweak (default), and strobe duty 006 (1.0ms---this is what the windows blur busters utility is calibrated for btw, its based on using the 1350 VT tweak) WITH the VT tweak (use the 60hz timing list for VT tweaks--that's why the monitor is reporting 60hz btw).
When using VT tweaks, try to avoid using a strobe duty of higher than 15 (2.5ms) at 120hz (you can see from the chart that 120hz is rated for 2.5ms maximum), and 18 (3ms) at 100hz (you can see again from the chart that 100hz is rated for 3ms maximum).
But when using VT tweaks, the 60hz pulse widths are used instead of the normal pulse widths, so 5ms is possible at strobe duty 030 (which is rated only for 60hz).
If you want to use 1502 VT at 120hz, you may need to change the timings.
Depending on your video card, DVI cable and monitor, you may get swimming pixels and corruption if the pixel clock is too high.
The default settings at 120hz will give you 396 MHz pixel clock at 1502 VT
(afaik, the default settings are 1920x1080(@120):
front porch 88,4
sync width 44,5
HT: 2200, VT (custom, though default value is 1125, 1500/1502 will put the pixel clock at 396 MHz)
if 396 MHz shows corruption and swimming pixels (usually on the right side of the screen or windows), you can lower it to 374 MHz--which should work fine, by using the following settings:
front porch 48,3
sync width 32,5
Horiz total 2080
Vtotal: 1502
That should work without corruption (using 'display mode' aspect settings will NOT work with any VT tweaks; the screen sizes will be miscalculated, wrong and may show corruption); if you want to use display mode aspect/resizing tweaks, switch to a resolution without a VT tweak (e.g. 100hz @ 1125 default VT).
You can tell from the 120hz listing (with some easy math), that 1.0ms persistence=strobe duty 012, WITHOUT a VT tweak (default), and strobe duty 006 (1.0ms---this is what the windows blur busters utility is calibrated for btw, its based on using the 1350 VT tweak) WITH the VT tweak (use the 60hz timing list for VT tweaks--that's why the monitor is reporting 60hz btw).
When using VT tweaks, try to avoid using a strobe duty of higher than 15 (2.5ms) at 120hz (you can see from the chart that 120hz is rated for 2.5ms maximum), and 18 (3ms) at 100hz (you can see again from the chart that 100hz is rated for 3ms maximum).
But when using VT tweaks, the 60hz pulse widths are used instead of the normal pulse widths, so 5ms is possible at strobe duty 030 (which is rated only for 60hz).
If you want to use 1502 VT at 120hz, you may need to change the timings.
Depending on your video card, DVI cable and monitor, you may get swimming pixels and corruption if the pixel clock is too high.
The default settings at 120hz will give you 396 MHz pixel clock at 1502 VT
(afaik, the default settings are 1920x1080(@120):
front porch 88,4
sync width 44,5
HT: 2200, VT (custom, though default value is 1125, 1500/1502 will put the pixel clock at 396 MHz)
if 396 MHz shows corruption and swimming pixels (usually on the right side of the screen or windows), you can lower it to 374 MHz--which should work fine, by using the following settings:
front porch 48,3
sync width 32,5
Horiz total 2080
Vtotal: 1502
That should work without corruption (using 'display mode' aspect settings will NOT work with any VT tweaks; the screen sizes will be miscalculated, wrong and may show corruption); if you want to use display mode aspect/resizing tweaks, switch to a resolution without a VT tweak (e.g. 100hz @ 1125 default VT).