3dfan wrote:
im just another crt monitor user which as been waitng for ages for a real replacement with no luck and dissapointed with modern monitor companies offerings trying to manipulate - cheat you with mediocre products.
+1
My last dissapoint was Asus TUF 2019 series, i have nothing against ASUS, i would say exactly the same of any other brand, and hope they fix in future.
VG27AQ (IPS) and VG27BQ (TN), when i read are capable of Adaptive Sync + Strobe, i was excited, thinking, let's see what Asus has managed to do. I read TFTCentral and Rtings reviews, double strobing issue at all frequencies
, and in HardForum topic abuot these monitors, users complain about to much crosstalk even only with strobe, without mix it whit Adaptive Sync
just give us your money, get your motion clarity and stop crying about side flaws, after all, what you want is "just motion clarity".
We would be lucky if it were true, because crosstalk issue break the motion quality. This is Benq/Zowie XL2720z, fine tuned...
and vellar instead of being suggested to research more the first pages from this topic, was suggested to buy this XG270 monitor which at its current state, has the same brigtness loss flaw his current monitor has and concerns him in blru reduction modes (Acer VG270U)
I got carried away by enthusiasm
also i did not find in that manual a mention of 60hz motion clarity compatibility so the minimum still being 75hz in the next firmware i guess?
This topic is for convince Viewsonic to add it.
But be aware, as
RealNC say in this forum, that LCD strobe flicker 60Hz is as intense as CRT at 30Hz
, due to current strobe tech is not the same as phosphor smooth decay.
Simulate CRT 60Hz phosphor decay in LCD strobe 60Hz is good for less flicker, but undesirable for motion quality, panning in CRT 60Hz a white moving object in a fullscreen black background, cause a long trail WhiteToBlack behind the white object. This same test in XG270 SingleStrobe 60Hz with strobe fast WhiteToBlack, for sure leave much less trail, but with heavy blink
The solution can be set a long strobe lenght at 60Hz for compensate, trade Flicker with MotionBlur.
I hope game developers take note of this problem, and stop limit games at 60FPS, is ridiculous. If a game is designed for console, and detect 60Hz HDTV, run at 60. But make the engine uncapped, and if port it to PC do not limit to 60FPS