BenQ XL2411Z Bad Ghosting?

[urut]

Ehh it must be driver bug or something.. Even on 120 vs 144 i feel the diffrence in smoothness, and now on 183 i didn't feel is more smoother than 144, so nvidia give's a prank to me i think :/

[Falkentyne]

Thanks,
I'm going to have Masterotaku try this.

Either this is an Nvidia driver bug or XL2720Z firmware is locked.
And I don't have Nvidia driver to be able to test this.
Because your resolution does not work at 144hz.

I tested over DVI. exact timings as yours, 144, 150...
Can you do me a favor?
if you still have time ok?

Restore your regular resoluitons, then run "RESET ALL.exe" in toastyX "CRU"
(then you need to run restart.64.exe to restart the NVidia driver).

Then try to create your resolution (144hz, 150hz ,then 183hz) in CRU instead of Nvidia CP.

Sorry for the trouble
Because on CRU, 144hz=black screen with your timing.

[urut]

Ok i will do this right now, give me 5-10 minutes and i reply back

[Falkentyne]

I was able to get 144hz to show display if I change 1100 to 1098 VT with your timings
But the screen has flickering pixel and shimmer all over. artifacts all over the screen

146hz worked but artifacts even more. Afraid to damage the monitor. I think horizontal total is too high...
147hz: out of range.
Firmware lock.

[urut]

Can't create with CRU, out of range error with timings i type in nvidia :/

[Falkentyne]

I know what is happening.
The firmware is locked.
Nvidia allows you to create GPU scaled resolutions even without "DSR"
You can upsample and downsample.

example, you can create 2560x1440 resolution and downsample it by having the "Active Pixels" 1920x1080.
That's a GPU scaled resolution. (OSD will report 1920x1080 if you do that).

The same things happen if you enter an invalid refresh rate or invalid resolution. You can test it but it won't save.
I guess it will save invalid refresh rates but not invalid resolutions.

I think whats happening is the driver is trying to GPU scale your resolution because the timings are invalid
So the driver is outputting 183 fps because it thinks it's 183hz even though its 144hz.
It's the same thing as 2560x1440 with 1920x1080 as "Active."

Everything I do on my computer, I use CRU, so everything is done from EDID override to monitor directly.
Firmware is hard locked to 146hz maximum

[urut]

So Falkentyne, sorry for fake alarm with 150++hz.