Explainer

Steam Frame has two routes to VR, and they ask different things of the hardware

Steam Frame can run software locally or receive PC-rendered video. Those modes divide the computing, power and timing problems differently.
Illustrative stock photograph of a VR headset in a laboratory. This is not Steam Frame.

Illustrative image: Unsplash contributor on Pexels

A wireless VR headset can carry the computer or borrow one. Steam Frame does both, which makes its most interesting feature the boundary between the two.

Valve's headset runs SteamOS on a Snapdragon 8 Gen 3 processor. It can execute software locally, but it can also receive images rendered by a separate PC. The screen is the same in either case. The work needed to put a convincing world on it is distributed very differently.

When the PC renders the scene

In streaming mode, the PC calculates the scene and encodes the resulting images. The headset receives that compressed video over the radio link, decodes it and presents it on its displays. Valve supplies a dedicated 6GHz wireless adapter for the PC connection; the headset also has separate wireless connectivity for other network traffic.

That arrangement gives the headset access to a PC's graphics performance without putting the PC's heat or mass on the wearer's face. It also creates a timing problem. Rendering, compression, transmission, decompression and display each consume part of the interval between a head movement and the corresponding image. More wireless bandwidth helps carry the data, but cannot by itself remove delays introduced elsewhere in that chain.

Local execution removes the streamed-video journey. It puts the rendering workload, and its power consumption, inside the headset instead. Battery capacity, cooling and sustained performance then become immediate constraints on what software can do.

There is a software translation task too. Valve's developer documentation distinguishes native Arm64 applications, Android software and the Windows games built for x86 PCs. Proton supplies compatibility with Windows software interfaces on Linux, while FEX translates x86 instructions for the Arm processor. These solve different problems; having one does not make the other unnecessary.

The physical design makes those operating constraints tangible. iFixit's teardown identifies a 20.9Wh battery in the rear headband, LCD display assemblies and an internal cooling fan. Moving the battery behind the head spreads the mass, but does not make its stored energy limitless. The teardown also finds that reaching the fan requires substantial disassembly.

Steam Frame therefore offers two useful ways to place the computing burden. A nearby PC can supply the graphics work through a tightly managed video link, or the headset can run compatible software on its own processor. Performance in one mode does not establish performance in the other: each follows a different route from application code to the image in front of the user's eyes.

Valve Steam Frame. Valve compatibility documentation. iFixit teardown.

Continue reading