5 ms·
Something I have been curious about – why is VR headset development going in the direction of cramming all electronics into a single component which sits on you
by paxys 5y ago
Something I have been curious about – why is VR headset development going in the direction of cramming all electronics into a single component which sits on your head, rather that the headset itself being a dumb terminal and the actual storage/processing done on some other box (which doesn't have to be a PC) sitting somewhere in your house and sending signals to it wirelessly?
- gorjusborg 5y agoI'd still be okay with wearing the compute, just put it on my back or something. Having a ton of weight on my head is tiring. The communicate via fiber or wire to a light headset.
- seanmcdirmid 5y agoLatency of wireless communication is non-trivial. Those extra 100 ms to transfer a frame buf will make the experience less.
- savanaly 5y agoWhat little I know about the subject suggests it has to do with retention. It seems users of VR are much more likely to pick it back up after the initial honeymoon phase has worn off if the whole "picking it back up" process is just strapping on a headset rather than involving a second device, pairing it, etc. The less friction the better.
- kanetw 5y agoYes, exactly. We want people to just put on a headset and use it, instead of having to boot Linux and plug everything in. God knows it's a pain when I'm developing with a tethered headset.
- rtkwe 5y agoBecause the PC or laptop required to run a dumb terminal well is more powerful than most people have. By selling an AIO unit you have a console like uniformity of hardware and ease of use experience for both the devs and the customers.
- soylentcola 5y agoThe flip side of this (much like with AIO PCs and "smart" TVs, but in reverse) is that I'd be a lot more likely to buy a less expensive client/terminal and connect it to a more powerful PC because if the headset - which is the thing trying to prove its usefulness - breaks or ends up collecting dust, I still have the PC which can power all sorts of other tasks and uses. If I spend all the dough on an AIO headset PC and it turns out to be underwhelming or I just never fit it into my long-term usage, then I've got a $2k+ computer I never use. Just as I'd prefer to separate the monitor from a PC or the media player from a TV, I'd be a lot more eager to try a headset if it wasn't attached to its own expensive PC.
- kanetw 5y agoThat's why we offer a tethered option, and why the compute unit is detachable and dockable.
- kanetw 5y agoLatency and bandwidth. We push about 3.4 GByte/s (or 27.5Gbit/s) to our displays. Even a 26Gbit/s DP1.4a HBR3 link needs display stream compression for that. So a wireless link will absolutely need strong compression. H.265 can push that to maybe (ballpark) 200Mbit/s, which is fairly feasible. But that will need to be evaluated and optimized for text quality and latency. Some googling suggests 100ms end-to-end latency as good. That's pretty high for VR, IMO. [Edit: fixed the DP1.4a bandwidth)
- akvadrako 5y agoYou can definitionally get lower latency with H.264 - somewhere around 5-10ms encode and 2ms decode. That's what makes Parsec and streaming gaming platforms possible even with all the other latencies involved. H.265 might be slower, but EVC, especially LCEVC, is supposed to be about 30% lower latency encoding than H.264.
- kanetw 5y agoInteresting. I wonder why the googled numbers were so high then. I'll take a look sometimes; wireless streaming would be cool.
- potatolicious 5y agoLatency, bandwidth (and with that, packet loss). Right now the closest tech to do this would be something like WiFi - but the latency is high, and the typical home's WiFi network bandwidth (practically due to the vagaries of radio) is not sufficient. A few reasons this is important: - latency in VR induces motion sickness and operates on a different scale than we're used to for regular network communications. A 50ms lag in a 2D video game is acceptable, a 50ms lag in VR will cause nausea and vomiting. This is a domain where single-digit milliseconds matter a great deal for user comfort. - resolution and refresh rate is everything - VR's viability in large part hinges on the resolution of the screens, which right now are somewhere between "poor" and "mediocre" - nothing so far has come close to replicating 20/20 vision. Moreover you need those screens to refresh far more quickly than a regular monitor - 60Hz doesn't cut it, 90Hz is basically the minimum. Streaming an uncompressed 8K stream at 90Hz over wireless requires more bandwidth than any existing standard can deliver. It's at the edges of our wired capabilities. Of course you can compress the streams, but that not only degrades image quality (which matters a great deal when the screens are replacing your eyesight) but also injects additional latency into the whole affair. It's theoretically possible - but would require developing a lot of custom tech that doesn't exist yet. It would also likely be highly sensitive to the exact particulars of the physical environment - one user may have a perfect experience while the other experiences so much packet loss/reduction in bandwidth that the whole experience is unusable.
- kanetw 5y agoYeah, the only way this is remotely feasible without massive latency and compression is a 802.11ay link, if it works when you're moving around. And since it's mmWave you'd need a base station in every room and 100Gbit ethernet to connect to it.
- deleted 5y ago[deleted]
- jjcm 5y agoI'd actually argue against this - I've been using my Quest recently to stream steam games over wifi on it, and I've been impressed with the capabilities. Overall the experience is seamless 95% of the time, and I don't notice any major differences between it and my HTC Vive. There are hiccups though - wifi will cut out briefly whenever there's any interference on that frequency, and you'll drop a few frames and quality will degrade for a couple seconds. Overall though I highly expect a stream over wifi 6 to be 100% usable for VR.