3 ms·
His math is way off, but the point still stands. The additional lag due to distance is noticeable above 5.000 km or so. Maybe it's good enough - but in VR, it m
by akvadrako 9y ago
His math is way off, but the point still stands. The additional lag due to distance is noticeable above 5.000 km or so. Maybe it's good enough - but in VR, it might be jarring.
- abetusk 9y agoFor context, the diameter of the earth is 12,742 km. So it would take roughly 30ms to make a round trip. Assuming that a signal need only traverse half the diameter as you can take the shortest arc, you get down to ~6371km which brings you back down in the range of 15ms. I assume the 15ms was chosen for the 60fps that VR needs to run at to be considered reasonable. If so, having a local machine handle redraws would be reasonable and requiring a 30fps update on all "agents" and other world elements would probably be pretty unnoticeable by most people.
- akvadrako 9y agoTypical transatlantic latency is way more than 15ms - more like 50 one way. To Asia and Australia is much more. Thats on top of processing and last mile delays. Anyone can notice the total latency in even a Skype conversation.