> The VR problem is latency. We
should be able to get sense/computation/display down to the 10-15ms required, but distance introduces additional latency, due to
c. If a ns is roughly a foot, 15ms is 15000 feet, gives a theoretical maximum diameter (not radius) for remote "city limits".
Wow, the VR problem is latency? Have you ever had a real-time conversation with anyone outside your hemisphere? If 15ms is 15,000 feet then 1/0.015 = 66 times that should be the speed of light, i.e. 300,000 km/s. Does that (66 x 15,000 ft = 300,000 km) seem even vaguely in the right ballpark to you?
You're off by a factor of 1000. It's 15 microseconds, not milliseconds. And incidentally, this might be a good excuse to go travel outside the country and meet people from elsewhere on the planet... you never know what you might learn about the world around you.
Wow, the VR problem is latency? Have you ever had a real-time conversation with anyone outside your hemisphere? If 15ms is 15,000 feet then 1/0.015 = 66 times that should be the speed of light, i.e. 300,000 km/s. Does that (66 x 15,000 ft = 300,000 km) seem even vaguely in the right ballpark to you?
You're off by a factor of 1000. It's 15 microseconds, not milliseconds. And incidentally, this might be a good excuse to go travel outside the country and meet people from elsewhere on the planet... you never know what you might learn about the world around you.