LG 27GK750F-B - 240Hz, 27" 1ms Blur reduction, Freesync

[k2viper]

hardware.info inputlag measurement is not relevant since they used 60hz Leo Bodnar lag tester.
There's playwares review in korean (read through google translate): http://playwares.com/dpreview/55780693#
They measured it with SMTT which is also used by tftcentral, and playwares result "2-4ms" lay pretty close to other fast gaming monitors tested by tftcentral also with SMTT: http://www.tftcentral.co.uk/reviews/asu ... 8q.htm#lag

Actually I dont think LG has real problems there, besides that growth of DPC latency A Solid lad found.

I tested 240hz with 2200 HT.
It works fine, no problems like stuttering, not working MBR and so, but also no decrease of DPC latency.
It should be other timings still not found. Or a driver version maybe.

[giubox360]

hardware.info inputlag measurement is not relevant since they used 60hz Leo Bodnar lag tester.
There's playwares review in korean (read through google translate): http://playwares.com/dpreview/55780693#
They measured it with SMTT which is also used by tftcentral, and playwares result "2-4ms" lay pretty close to other fast gaming monitors tested by tftcentral also with SMTT: http://www.tftcentral.co.uk/reviews/asu ... 8q.htm#lag

Actually I dont think LG has real problems there, besides that growth of DPC latency A Solid lad found.

I tested 240hz with 2200 HT.
It works fine, no problems like stuttering, not working MBR and so, but also no decrease of DPC latency.
It should be other timings still not found. Or a driver version maybe.

Yeah the input lag should be that because I feel it fast.
(the only thing is about washed out colours in very fast movements, but I guess is normal for a TN panel)
Very nice test how do you feel 2200 HT better or worse with MBR?

[k2viper]

It should be worse because I rolled back VT from 1304 to default 1180, to have dotclock headroom needed for 2200 HT.
I havent tested this res, only checked that 2200 HT resolution at 240hz had no effect on DPC.

[GammaLyrae]

hardware.info inputlag measurement is not relevant since they used 60hz Leo Bodnar lag tester.
There's playwares review in korean (read through google translate): http://playwares.com/dpreview/55780693#
They measured it with SMTT which is also used by tftcentral, and playwares result "2-4ms" lay pretty close to other fast gaming monitors tested by tftcentral also with SMTT: http://www.tftcentral.co.uk/reviews/asu ... 8q.htm#lag

Actually I dont think LG has real problems there, besides that growth of DPC latency A Solid lad found.

I tested 240hz with 2200 HT.
It works fine, no problems like stuttering, not working MBR and so, but also no decrease of DPC latency.
It should be other timings still not found. Or a driver version maybe.

Yeah the input lag should be that because I feel it fast.
(the only thing is about washed out colours in very fast movements, but I guess is normal for a TN panel)
Very nice test how do you feel 2200 HT better or worse with MBR?

I still like the Bodnar test because it's a good way to see if there's any additional latency in 60hz mode. Of course, it always needs to come with the qualifier that up to 16.xms is normal due to how scan out works. The comparison to crt latency is nice too, but doesn't present the full context of the situation.

I went ahead and pulled the trigger on this monitor. I'm not going to sweat any latency that has to be measured in microseconds. There's 1000 of those in a single millisecond, I do not believe they could ever contribute to any delay you could see or feel. Scan out lag, processing delays, and pixel transitions (all of which get measured in milliseconds) are going to be what you see and feel.

[A Solid lad]

I'm just a bit scared about 2 things:
1) games where I can't keep 240 fps (so I can't set any MBR to keep the game sharp )
2) the blue trials and/or overshots with the fast/fastest overdrive.

One last thing, can you please explain to me why do you think that the alienware is less washed out than the LG, please?
why do you think also that the alienware is more responsive while playing?
Thanks in advance.

I'm too tired to comment on your first qualm, as it has been discussed way too many times on this forum
My reaction to the second: ummm.... you can just leave the OD setting on normal and avoid almost all overshoot? nobody forces u to use "fast" or fastest"

Hmm, on the LG, when you're moving a window around on the desktop with text in it for example... you can tell that stuff s just more smeary, compared to the Dell... idk what's the cause of of it.
I can see this even when I scroll this very page smoothly, in which I'm writing this reply.
On the LG, the lines of the letters get more thin, while I'm scrolling... and their outline is smeary.
On the Dell, they retain their thickness better, and less smear is present around them...
I think that's the most easy way to demonstrate what I'm talking about.
Ingame, this contributes to a smeary image, when panning... and this might contribute to the overall less responsive feel.

[A Solid lad]

.

[A Solid lad]

I went ahead and pulled the trigger on this monitor. I'm not going to sweat any latency that has to be measured in microseconds. There's 1000 of those in a single millisecond, I do not believe they could ever contribute to any delay you could see or feel. Scan out lag, processing delays, and pixel transitions (all of which get measured in milliseconds) are going to be what you see and feel.

Again, I'm not too worried about those microseconds either... I'm worried about what's causing them.

[GammaLyrae]

I went ahead and pulled the trigger on this monitor. I'm not going to sweat any latency that has to be measured in microseconds. There's 1000 of those in a single millisecond, I do not believe they could ever contribute to any delay you could see or feel. Scan out lag, processing delays, and pixel transitions (all of which get measured in milliseconds) are going to be what you see and feel.

Again, I'm not too worried about those microseconds either... I'm worried about what's causing them.

Understandable. I got latency monitor installed the other day and discovered that my network driver was having nasty spikes in activity, demanding more time and resources than even the gpu under load. I was able to find a driver that fixed the latency spikes, which fixed a problem I was having in one game.... But I am reasonably certain that if the latency is consistent under idle or load conditions without unexplainable spikes, you're probably fine. Just my opinion (I'm not exactly a hardware engineer)

[A Solid lad]

Anyway, here are some more findings from me regarding dpc latency:
https://www.youtube.com/watch?v=kYE9BmVzfDg

And for giubox360: In this video, you can find Ghosting/Pursuit camera tests for the AW2518H, both 240hz non-strobed and 144hz ULMB:
https://www.youtube.com/watch?v=9VbVWY1-FPc

[A Solid lad]

I went ahead and pulled the trigger on this monitor. I'm not going to sweat any latency that has to be measured in microseconds. There's 1000 of those in a single millisecond, I do not believe they could ever contribute to any delay you could see or feel. Scan out lag, processing delays, and pixel transitions (all of which get measured in milliseconds) are going to be what you see and feel.

Again, I'm not too worried about those microseconds either... I'm worried about what's causing them.

Understandable. I got latency monitor installed the other day and discovered that my network drive was having nasty spikes in activity, demanding more time and resources than even the gpu under load. I was able to find a driver that fixed the latency spikes, which fixed a problem I was having in one game.... But I am reasonably certain that if the latency is consistent under idle or load conditions without unexplainable spikes, you're probably fine. Just my opinion (I'm not exactly a hardware engineer)

You're probably right... sadly though, I'm kind of a perfectionist, so as long as I see people like giubox360 getting single digit DPC latency averages at idle, I won't rest until I can get my setup to perform like that as well.