Stream to 3D Performance Guide

Updated 19 July 2026

This page explains the main performance bottlenecks and the quickest changes that improve smoothness in Play/Stream/Convert.

If you see an LVE0xx error code, start with Licensing & Activation and Error Codes.

Start here (fast improvements)

Start with Half formats (HSBS/HTB) for compatibility and performance. See Settings → Format.
For a 4K or 8K source, resize the input to the detail the target output can actually retain rather than processing unused pixels.
If Play or Stream cannot stay smooth in real time, use Convert when your edition includes it. Offline conversion removes the requirement to finish each output frame in real time, but the target player must still decode the resulting resolution and frame rate. See Video File Conversion.
If audio stutters or stops with a demanding output, test a lower resolution and Half layout. The cause may be conversion, encoding, network delivery or the receiving player's video limit rather than the audio track itself.
If streaming, start with HTTP and test the stream URL locally first (same PC). See Streaming.

Why formats matter (Half vs Full)

Full formats keep a larger combined frame and are more demanding. Use one only when the Windows output, receiving player and device can all accept it. Half formats are often the most compatible and reliable starting point.

Upscaled Half is useful when a player requires a Half-labelled layout but the output path can carry a larger frame and retaining more source detail matters. It adds work and provides no benefit when the desktop, player or device scales the result down again.

If you’re trying to diagnose a stutter or lag problem, reduce load first with a Half format, a suitable input resize and a short clip so you can isolate whether the limit is conversion, encoding, network or playback.

Encoding and graphics drivers

Stream and Convert need the encoding application to be detected in Settings → Tools.
Optional graphics-accelerated encoding depends on a compatible NVIDIA or AMD graphics driver. If Stream to 3D reports a compatibility error, update your graphics driver or use software encoding.
For advanced settings, see advanced streaming and conversion options.

Frame rate and interpolation

A headset refresh setting of 90 Hz or 120 Hz is not the same as the video frame rate. A 24, 25 or 30 FPS source can be displayed while the headset refreshes more frequently; Stream to 3D does not need to create 90 or 120 unique frames solely to match that display mode.
Start with the source/sample frame rate. Higher output rates require interpolation and add significant processing work.
GPU model, VRAM capacity and CPU core count alone cannot guarantee a target rate. Input and output resolution, layout, interpolation, capture, encoding, network and player decoding all contribute.
If a higher rate is not stable in Play or Stream, use Convert when the edition includes it and verify that the target player supports the resulting rate.

Network limits (streaming)

Make sure the client device is on the same LAN/Wi‑Fi as the PC running Stream to 3D.
If streaming is unstable, reduce resolution and/or bitrate first.
If it works locally but not on the device, check VPN/firewall routing. See Streaming first checks.

Live/screen capture performance

Reduce capture frame rate and/or capture region to match your hardware.
Start with Screen Capture and PC Screen or Live Video Conversion to 3D.

Before contacting support

To get the fastest resolution, include:

Your store (Steam/Gumroad/Itch/etc) and Stream to 3D version.
What workflow you’re using (Play/Stream/Convert/Live Sources).
What output format you selected (HSBS/HTB/Full, etc).
Logs from Logs & Diagnostics.