Performance
Latency, visual quality and bitrate in pixel streaming: what the encoder and WebRTC settings do, how to measure before tuning, and how to publish results others can compare.
Every pixel streaming setting that affects quality also affects latency, bandwidth or GPU load, and the trade-offs differ by codec, resolution, frame rate and network. Epic’s reference documentation lists the encoder and WebRTC settings; what it cannot tell you is how they behave on your hardware and your users’ networks.
The articles in this hub therefore start with measurement: what end-to-end latency actually means for an interactive stream, which numbers the engine and the browser expose, and how to record conditions precisely enough that a result can be reproduced. Tuning guides follow from that, and every benchmark published here states its hardware, software, network conditions, methodology, units and limitations.
Troubleshooting guides
Symptoms, causes, diagnostic checks and verified fixes.
- Troubleshooting
UE 5.7 and 5.8 Pixel Streaming crashes, VRAM leaks and disconnects: the NVENC D3D12 bug and its fix
UE 5.7 and 5.8 Pixel Streaming apps that freeze, leak video memory or die with DXGI_ERROR_DEVICE_HUNG after a viewer connects: how to recognise the NVENC D3D12 encoder bug and the flag that fixes it.