Originally Posted by premierplayer
What is acceptable input lag and how can we gauge it.
Mainly by playing.
If a game feels "sluggish" with the Game Low Latency feature on, like the action on-screen is falling behind button presses and you can't perform in-game as you feel you should, then this is unacceptable. If the game seems to be responding like it should when you are pressing buttons, that is acceptable.
The easiest way I test lag in action is to play a pinball game like Pinball FX2 (Xbox One), Zen Pinball 2 (PS4), or Pinball Arcade (both systems) - the flippers should trigger at the precise moment of pushing the button. Lining up shots should be precise. If the flippers are late and shots are missed, then the lag is an issue.
Everyone has their own sensitivity to input lag, and what it noticeable to one person might be perfectly fine for another.
For single-player games, my rule of thumb:
- ~20ms is pretty much perfect -- super sharp, precise, and undetectable lag to all but the most frame-sensitive player.
- ~45ms is solid, most people should have no issues playing single-player games.
- ~60ms starts to feel a touch laggy, but many people can compensate and still have no problems adjusting gameplay.
- ~ 90ms and beyond can be felt, and many gamers won't want to play with this much lag.
A huge YMMV to the above.
Originally Posted by Optum88
Thank you for this, but find it contradicting. First, they are trying to pull down the HDR10 input lag to near 0ms, but then states that would mean - HDMI 1-4 in HDR10 = 45ms. So which one is it? Can someone help me understand this? Does it mean the lowest possibly is 45ms for 4k HDR? Or that they are working to bring HDR10 input lag to near 0ms, but for now, we'll get 45ms. Can someone please clarify. Thanks so much in advance.
As mentioned before, HDR10 on Vizio P-series now adds zero extra
lag with the new beta firmware and beyond, so it's the same lag as SDR, which on HDMI 1 through 4 is solid ~45ms input lag. Before the recent beta firmware update, HDR added an extra ~15ms because it was going through the Dolby Vision chip, but this is no longer an issue anymore.