(enlgish is not my native, it's little bit hard for me to explain:D, but I will try)ItwasLuck wrote: ↑24 Jun 2020, 15:17I am not going to comment on RTINGS, as I believe their measurements are 100% accurate if comparing different monitors from their site. Getting 1.7ms @ 280Hz is still surprising, but keep in mind that is 240Hz vs 280Hz.sk1p wrote: ↑24 Jun 2020, 08:32I bought XL2540 after reading review about it on RTINGS and input lag was horrendous, but they admit it has 3.7ms. After I exchanged XL2540 to AW2518HF which has 4-5ms according to some reviews, but I felt that AW2518HF is faster than XL 2540 in term of input latency. So after that I with suspicious read RTINGS reviews. I believe to TFTcentral, I bought XF252QX with 3.3ms accordind to TFT and YES it was faster then AW2518HF. Now I have VG279QM for several months and really happy with it in CS GO and agree with TFTcentral measurements(2.3ms), RLCScontender has 2.4ms, so I guess Acer really faster and give it a try. 1.7ms on RTINGS really weird in 280hz mode, because I feel myself that in 240hz mode input lagh is lower than in 280hz, I think their methodology is incorrect.. TFTcentral and RLCScontender measurements are right.
It is quite interesting that you find 240Hz to give you less lag than 280Hz and that is most likely due to the response time. Depending on what OD settings you went with, it is possible that the response time isn't fast enough to run fully compliant at 280Hz. But input lag is definitely less at 280Hz vs 240Hz. If you are not running ELMB, try setting OD @ 80 and give 280Hz another try.
The Acer is definitely faster (least input lag) and I believe it's worth trying out. As for whose measurements are correct? I believe they are all correct, they simply use different testing methodologies and it would be wrong to point fingers on a particular site just as Chief mentioned earlier.
It's possible you are confusing response time with input lag, these are the two most important factors in determining how snappy a monitor feels (apart from refresh rate). However, if you are gaming at sub-200 FPS, I definitely think the Acer will give you an edge.
I'm not using ELMB. I like to use 240hz and 60 OD mode, 280hz and 60 OD has exactly higher input lag, 280hz with 80 OD is close to 240hz and 60 OD, but I get my best flicks and insane shots in CS GO in 240hz and 60 OD mode.
Why this theme bothers me?
I have been playing fps games from 2000, like Quake 3 arena, CS1.1 then 1.3 and 1.6(was played in PRO league in 2004-2006), and I used CRT monitors and know what is fast consistent input without any latency. Actually in 2000-2006 I never heard such term as input lag.
As from win7 and m_rawinput 1 was invented in CS my war with input latency started))
It happened cause I always used high sensitivity, had 3.75 sens with 400dpi in 2004-2006 and I mine aim was very snappy and consistent. But after m_rawinput 1 was invented my confidence dissapeared and strange mouse feeling has come.
My subjective opinion that CS GO engine has input lag itself and people have many variants how to avoid this. m_rawinput 1 adds slightly input latency, there is old topic about that https://www.overclock.net/forum/375-mic ... o-tf2.html
Many guides recommends to use low sensitivity for consistent aim, actually I think it's just another way how to fight with input latency, but I don't like to wave my mice all over the pad)). So what I want to said that many people who use low sensitivity probably won't find input lag with 280hz and 80OD, but with high sensitivity you can feel any bad impact on snappy feeling, with 240hz and 60OD I get best results in game than with 280hz and 80OD. Now I optimized my settings with VG279QM that I can be very consistent and snappy with high sensitivity in CS GO. What I want to say that lowest input lag gives me advantage with high sensitivity that feeling is very close or the same to CRT monitors and my 2004-2006 game sensitivity. (I understand it will be advantage for everybody:D, but may be not so much for the guys with low sens). All my conclusions made on my own experience and I'm not trying to persuade smb that it's definely right way of monitor setting.