←back to thread

Steam Frame

(store.steampowered.com)
880 points Philpax | 1 comments | | HN request time: 1.791s | source
Show context
modeless ◴[] No.45904494[source]
Foveated streaming! That's a great idea. Foveated rendering is complicated to implement with current rendering APIs in a way that actually improves performance, but foveated streaming seems like a much easier win that applies to all content automatically. And the dedicated 6 GHz dongle should do a much better job at streaming than typical wifi routers.

> Just like any SteamOS device, install your own apps, open a browser, do what you want: It's your PC.

It's an ARM Linux PC that presumably gives you root access, in addition to being a VR headset. And it has an SD card slot for storage expansion. Very cool, should be very hackable. Very unlike every other standalone VR headset.

> 2160 x 2160 LCD (per eye) 72-144Hz refresh rate

Roughly equivalent resolution to Quest 3 and less than Vision Pro. This won't be suitable as a monitor replacement for general desktop use. But the price is hopefully low. I'd love to see a high-end option with higher resolution displays in the future, good enough for monitor replacement.

> Monochrome passthrough

So AR is not a focus here, which makes sense. However:

> User accessible front expansion port w/ Dual high speed camera interface (8 lanes @ 2.5Gbps MIPI) / PCIe Gen 4 interface (1-lane)

Full color AR could be done as an optional expansion pack. And I can imagine people might come up with other fun things to put in there. Mouth tracking?

One thing I don't see here is optional tracking pucks for tracking objects or full body tracking. That's something the SteamVR Lighthouse tracking ecosystem had, and the Pico standalone headset also has it.

More detail from the LTT video: Apparently it can run Android APKs too? Quest compatibility layer maybe? There's an optional accessory kit that adds a top strap (I'm surprised it isn't standard) and palm straps that enable using the controllers in the style of the Valve Index's "knuckles" controllers.

replies(10): >>45904910 #>>45905167 #>>45905538 #>>45905540 #>>45905841 #>>45906677 #>>45906840 #>>45906875 #>>45907352 #>>45908497 #
monocasa ◴[] No.45905167[source]
Foveated streaming is wild to me. Saccades are commonly as low as 20-30ms when reading text, so guaranteeing that latency over 2.4Ghz seems Sisyphean.

I wonder if they have an ML model doing partial upscaling until the eyetracking state is propagated and the full resolution image under the new fovea position is available. It also makes me wonder if there's some way to do neural compression of the peripheral vision optimized for a nice balance between peripheral vision and hints in the embedding to allow for nicer upscaling.

replies(5): >>45905184 #>>45905232 #>>45906440 #>>45906635 #>>45907062 #
cube2222 ◴[] No.45905184[source]
They're doing it over 6GHz, if I understand correctly, which with a dedicated router gets you to a reasonable latency with reasonable quality even without foveated rendering (with e.g. a Quest 3).

With foveated rendering I expect this to be a breeze.

replies(1): >>45905354 #
monocasa ◴[] No.45905354[source]
Even 5.8Ghz is getting congested. There's a dedicated router in this case (a USB fob), but you still have to share spectrum with the other devices. And at the 160Mhz symbol rate mode on WiFi6, you only have one channel in the 5.8GHz spectrum that needs to be shared.
replies(2): >>45905410 #>>45906901 #
1. zamadatix ◴[] No.45906901[source]
You're talking about "Wi-Fi 6" not "6 GHz Wi-Fi".

"6 GHz Wi-Fi" means Wi-Fi 6E (or newer) with a frequency range of 5.925–7.125 GHz, giving 7 non-overlapping 160 MHz channels (which is not the same thing as the symbol rate, it's just the channel bandwidth component of that). As another bonus, these frequencies penetrate walls even less than 5 GHz does.

I live on the 3rd floor of a large apartment complex. 5 GHz Wi-Fi is so congested that I can get better performance on 2.4 in a rural area, especially accounting for DFS troubles in 5 GHz. 6 GHz is open enough I have a non-conflicting 160 MHz channel assigned to my AP (and has no DFS troubles).

Interestingly, the headset supports Wi-Fi 7 but the adapter only supports Wi-Fi 6E.