Pixel Streaming: a 3D experience in the browser

Remote render, browser, and session control

1. Unreal application / render
2. Encoding + connection
3. Browser: picture + audio
4. Action → application

Pixel Streaming lets Unreal run and render an application on another computer and deliver picture/audio over WebRTC to a browser that sends actions back. It does not turn Live Link into a video call. Prepare the figure or scene as an application with a complete operating workflow.

• Versions: identify Unreal, Pixel Streaming/Pixel Streaming 2 plugin generation, and matching infrastructure branch. Use documentation and infrastructure that match that version.
• Resources: survey OS, compatible GPU/encoder, target resolution, audio, browser/device, and network. A GPU specification does not establish scene performance.
• Sessions: define whether several viewers share one state, one person controls it, or every visitor needs an independent instance. Resource and operational needs differ.
• Interface: limit available actions, show loading/disconnection, allow session reset, and provide an alternative to gestures or phones. Do not enable a microphone if the experience does not need it.

Epic describes signaling and, depending on the network path, STUN/TURN. Its reference infrastructure alone is not a complete production service. Before contracting, assign responsibility for hosting, access, capacity, and support, and identify compute, data transfer, and auxiliary service costs. Test how many simultaneous sessions and actions the configuration supports before setting service capacity.

Proposed rehearsal: final scene/device, user arrival/departure, simultaneous actions, link loss, and return. Measure visible response from the visitor’s action alongside render performance. If the route is unsuitable, provide an operated local station or an approved video walkthrough. Choose according to the objective and rehearsal results.