If the machine doing the streaming is on the local network maybe.
VR is not a forgiving environment for latency. If your target 72fps (Quest), about 862 miles is an upper bound for distance. That's just to get data round-trip at fiber speed, additional latency sources (wifi, rendering, encoding, wifi again) are going to make things worse. Prediction and "timewarp" only get you so far.
I'm all for wireless headsets to eliminate the tether when using a PC, but to me the Quest is compelling primarily because it's standalone. I can bring it almost anywhere (empty warehouse, a large field outside, hotel rooms) and not need to worry about lugging a bunch of extra gear.
It's also really compelling for quick product demos if that's your thing. We can keep builds of software installed on a headset that can go from packed in a small hard-case to ready to show off in about the time it takes to boot.
VR is not a forgiving environment for latency. If your target 72fps (Quest), about 862 miles is an upper bound for distance. That's just to get data round-trip at fiber speed, additional latency sources (wifi, rendering, encoding, wifi again) are going to make things worse. Prediction and "timewarp" only get you so far.
I'm all for wireless headsets to eliminate the tether when using a PC, but to me the Quest is compelling primarily because it's standalone. I can bring it almost anywhere (empty warehouse, a large field outside, hotel rooms) and not need to worry about lugging a bunch of extra gear.
It's also really compelling for quick product demos if that's your thing. We can keep builds of software installed on a headset that can go from packed in a small hard-case to ready to show off in about the time it takes to boot.