I can pretty reliably tell if I’m playing on a PST or EST (North America) server, with the latter having 50-60ms latency compared to a PST server with 20-30ms due to differences in distance. It’s not massive, but on EST servers everything is ever so slightly less responsive, and it’s particularly visible in combat where many abilities are being used rapidly and outcome is dependent on order of operations.
The differences starts becoming obvious when crossing the 80-90ms latency and unmistakable at 120ms+.
I would agree that it would be difficult to tell the difference in a one-off test but when it’s something you’re actively doing for long stretches of time it’s easy to pick up on.
Once I moved and got onto broadband, and found myself with a miraculous 100ms ping, I basically had to learn the game all over again as my instincts would cause me to try to do actions I couldn't yet do, since I wasn't quite done casting a spell, harvesting a node, etc.
Later on I changed servers and was below 80ms ping, and the difference was again palpable but not game changing.
Maybe there are circumstances where 100ms+ latency is not noticeable, but I suspect they are few and far between if you're actually paying attention.
See it happening is very different from noticing lag. Here's a gif I like to reference when trying to determine how noticeable a lag spike is in milliseconds. For me it become unnoticeable at a 30ms lag spike. But 100ms is very plainly obvious.
Interesting. I still notice it at 20 ms, but not at 10 ms.
Average ping is 63 ms. Even that latency is noticeable - more typing errors for sure. I never connect without mosh.
Yea, author never played MMOS or FPS games online?
Going from 20ms to 100 is going to be VERY noticable.
There are a number of confounds for measuring things like this because we're often not talking about exactly the same thing: for example, the times needed to perceive motion, size, color, orientation, and recognize something are all different (to a first approximation, the relative latencies are roughly what you'd expect if the most important selection criteria was a relatively weak fructivorous ape trying not to get eaten) and there are measurable differences between how you respond to things you're predicting will happen, continuous motion, or truly unexpected events. This also varies considerably for novel and trained behavior — e.g. if you're waiting to shoot when you see a pixel change, your body is primed and presumably quite well practiced vs. something random happening in a video. All of that means that something like extra keyboard latency is especially noticeable because you're initiating the action, it's extremely practiced, and you thus have a well-honed expectation for when the response should be visible
The most responsive games achieve sub 30 ms motion to photon locally, with proper hardware.
So he's making the opposite argument you think he's making - he agrees with you.
I remember Dan posting that he typed at ~120wpm somewhere. 120wpm is 0.002 words per ms or 0.4 words per 200ms. Wouldn't one notice if they're almost halfway through a word and nothing has shown up on the screen?
There is quite a delay between the eye detecting something and it being consciously processed to the point of being used in decision making. Away from built-in reactions (move hand away from burning sensation and so forth) that are not consciously controlled there is a sometimes surprising amount of latency in our view of the world. It is surprising because the brain does a rather good job of smoothing it out with guesses/predictions such that you generally don't notice.
Only when things fall outside the range of patterns you naturally cope with or expect because they are consequences of your own actions, do you really become aware of them. So he might not notice usually, but would if an error or something else unexpected occurred.
This is why 100ms, or even sometimes 200ms, is fine for many things, but others cause irritation despite delays of 40ms or sometimes significantly lower. The brain smooths out what it can, the rest sets of warnings of potential trouble.
We may be slow to react to sudden events, but we are very good at noticing the lag for predictive events (keyboard typing, piano playing, ...).
[0] This is the first one about the recent experiments: https://www.youtube.com/watch?v=VyIk0IqC7SQ
For higher fidelity tasks like mouse movements, I'm pretty sure I can notice the difference between 16ms at 60hz and 8ms at 120hz. But it's hard to tell if that's because of pure latency or smoothness, I would suspect the latter.
There is definitely a big difference between consciously noticeable latency and latency that has an effect on people.
Yes, to get to the point where a person can notice that latency is occurring and can call it out, you need to be in the 100ms range.
But if you want to make a VR system that doesn't make most people physically ill, you have to get "motion-to-photon" latency down to around 13ms (75hz). Even at that range, you still get a relatively large portion of people experiencing issues; I'd estimate 20%. At 90hz, you can get that down to about 10%. At 120hz (less than 9ms!), I haven't seen specific numbers, but my gut feeling from my own work with users is that it's lower enough to care about the extra work to hit that target. I suspect that we can't be fast enough on this issue, that 240hz, maybe even 1000hz, will be necessary to get down to 1%.
Luckily, most VR systems today have asynchronous reprojection systems to decouple view movements from application updates (to a degree). It is an extrapolation system, so there are some artifacts, especially around the edges of objects, especially if there is a huge difference between application update rate and view update rate. But I've seen applications running updates at 30fps, which should be headache inducing for sure for the vast majority of people, but they're running on headsets with a 120hz refresh rate and all you really notice are that animated objects look a little choppy.
Typing on a computer is a different story. The latency perception via the eyes is very different than through the ears.
There are players that can do OTGF move every time they try.
My audio interface for connecting my keyboard/guitar to my PC is USB-C. I tried USB2 devices and find they have too much latency. It's very noticeable. USB-C has 1ms latency or less.
It's a world of difference playing FPS shooters online between a 50ms ping and a 100ms ping. If you care about your aim, 100ms ping is barely playable.
That has nothing to do with latency. Human nerve conduction velocities just aren't quick enough for things like that to be done closed-loop under the control of the brain - it's just physically impossible.
Although the person doing the action may feel otherwise, that's just a well-trained sequence of actions performed open-loop.
In games with really bad netcode it can get ridiculous, influencing the entire gameplay - for example in PUBG beta, which had about 200-300ms of actual client-to-client latency due to the very low server tickrate, you had to avoid running directly towards the corner to look around it, as enemies could see you running out in the open for a split second then rubberbanding back.
Any latency, whether it's hardware, software or server, drops their performance significantly. It's at a point where they only play/practice under prime conditions, as their sensitivity is such that they will throw themselves off by practicing with more latency than they normally do.
It's crazy.
Play Zandronum on 150ms server against people with 30ms. You will go for a new mouse (or maybe even a keyboard and monitor) in half an hour.
Are you sure that's not just USB 2.0 interface being shit ? USB2.0 is certainly fast enough to have sub-ms latency.
I actually wondered about how to go with testing USB interface latency, maybe I should test mine when I have slow weekend...
I can tell when there's an extra render in a React app, on an input or just when something renders slightly later than expected like an update is being done in a useEffect after the first render, and I agree that it's really annoying. However, the input latency of a React app should be less than 16ms. There's nothing intrinsic to React (or any JS framework) that means there has to be any appreciable lag. Obviously there are badly written ones that do things very poorly, but if you find one like that you should vote with your feet and move to a competitor.
What if there are no well written ones? No competitor to move to? I for one haven't seen a single React app that wasn't annoyingly slow, under the standards we're discussing here.
> There's nothing intrinsic to React (or any JS framework) that means there has to be any appreciable lag.
And yet, for common SPA frameworks, it seems it's always there. So if it's not the framework and the language, then something common in the overall process of frontend dev is a likely candidate.
If that's the case then React is a huge problem.
I've seen lots of apps that nail 60fps that are written in React though, so I don't think it is the case.
Case in point...
My previous iPhone had 60Hz refresh rate, that equates to ~16ms.
My new iPhone has 120Hz refresh rate, that equates to just ~8ms.
I can absolutely tell the difference in the display between these two devices when I scroll.
There are two other ways scrolling on a 60Hz vs 120Hz phone would allow you to tell the difference: the increased smoothness of the scroll (not related to latency at all) and how far the content lags behind your finger. The content lagging behind where you initially touched does allow you to experience the latency, but that is more of a visual only experience than a temporal one.
Apple reduced the latency in its pencil from 20ms to 9ms. It's well regarded that the reduction of 11ms in latency is very much noticeable.
It's different for where you don't have same senses for both. "Pressing" a key is feeling + sound but reaction is change in image, you don't see keyboard and screen at same time so it feels more tolerable.
It's not really more tolerable, unless you never experienced low latency here, and your brain is used to the effect of a key press being perceptually immediate.
https://www.researchgate.net/publication/259490307_Detecting...
>My gut is that there's a lot more to this, and that it's not broadly true.
Which is why that quote is from list of "counter-arguments people say" and debunked by author...
> I live in the UK and have worked from Australia a few times, and the latency is around 220ms. When typing over SSH, the latency is very noticeable.
You don't have 220ms latency. You have latency of your whole system plus that extra 220ms
My gut is that there's a lot more to this, and that it's not broadly true.
I live in the UK and have worked from Australia a few times, and the latency is around 220ms. When typing over SSH, the latency is very noticeable. Not in terms of pressing a key and feeling lag in it showing up, but in a feeling of sluggishness when typing more than a few words at a time. I also notice this feeling in web apps that use React managed inputs for example.
My guess is that while 100-200ms isn't noticeable in one instance, adding that to every interaction in a system that has multiple interactions per second is noticeable.
A similar comparison is that I can't detect audio and visuals being incorrectly synced with much less than 200ms precision for individual beeps, however if I watch someone talking on a TV that's 30ms out I can tell something is wrong (even if I can't tell which direction).