Xreal One Pro+ PC streaming apps tested for stereo

Time needed about 30–45 minutes end to end

The steps

1. Open the Xreal companion appsLaunch Ultraxreal or Xreal GlassesControl and the Xreal desktop client if available; keep status or pairing screens visible.You should see: The companion app lists the One Pro+ as connected or ready to pair and shows any firmware or app update prompts.
2. Connect the One Pro+ wired to the PCPlug the One Pro+ directly into a USB‑C or Thunderbolt port on the PC using a known good cable; avoid hubs for this step.You should see: The PC shows a connected display or the Xreal client shows an active wired session and the companion app shows the glasses connected.
3. Run desktop mirroring testStart the Xreal client mirroring feature or use the OS display duplicate to show your desktop in the glasses at a fixed resolution.You should see: You see a stable 2D desktop image in the glasses with readable UI elements and no head‑tracking jitter.
4. Launch SteamVR and check feed typeStart SteamVR on the PC and run a simple stereoscopic test scene or a SteamVR Dashboard that renders different content to each eye.You should see: If SteamVR supplies native stereo, the glasses show separate left and right images; if you see a mirrored desktop window, the feed is 2D.
5. Test Virtual Desktop over Wi‑FiSwitch the One Pro+ to Wi‑Fi, run Virtual Desktop on PC and glasses, connect both to the same 5 GHz network and start a high‑motion scene.You should see: You see a fluid stream with head tracking; motion is smooth and audio/video sync is reasonable.
6. Run a VRidge/ALVR conversion testInstall and start VRidge or ALVR on the PC and the client, then stream a game or stereoscopic demo routed through the converter.You should see: The glasses receive a stereo‑like image; inspect for ghosting, doubled edges or parallax errors during head movement.
7. Measure latency with a frame triggerRun a flash test on the PC (white→black) while recording both the PC monitor and the glasses view with a second camera; count frames between flash and glasses response.You should see: You can count a consistent frame difference between the source flash and the glasses view; write down the frame count and camera frame rate.
8. Document results and record short clipsSave labeled clips for each test and note which produced native stereo, converter stereo or only 2D mirroring, plus measured latency.You should see: You have a folder with named clips and a short text file recording pass/fail for each test and measured latency.
9. Decide based on acceptable fallbacksCompare measured latency and stereo results to your needs; plan hardware changes if you require true stereo low‑latency gaming, otherwise accept desktop or Virtual Desktop use.You should see: You reach a clear decision: the One Pro+ meets your use case, or you have a list of port/router/PC changes to try next.

Xreal One Pro+ PC streaming apps — what to expect

Different streaming apps behave differently on the Xreal One Pro+. Desktop mirroring always yields a flat 2D image. Virtual Desktop over a strong 5 GHz link with hardware encoding gives the best latency for productivity. SteamVR needs a bridge that exposes left/right frames to deliver true stereo. Converters add latency and visible artifacts.

Which streaming scenarios matter and how they differ

Distinguish four practical paths: native stereo from VR apps, Wi‑Fi PC streaming, converter apps that repackage 2D into stereo, and simple desktop mirroring. Each path differs in whether the glasses receive separate left/right images, how much latency appears, and what visual artifacts you will tolerate.

• Native stereo VR (SteamVR): requires the app or a bridge to deliver separate left/right frames.
• Wi‑Fi streaming (Virtual Desktop): sends a compressed video stream; latency depends on 5 GHz quality and encoder.
• Converters (VRidge/ALVR): synthesize stereo from a single stream and often produce ghosting or parallax errors.
• Desktop mirroring: stable 2D image with the fewest integration steps but no depth.

How to run the 10–15 minute compatibility and stereo test

Run a short sequence to verify pairing, feed type and latency. Install Steam + SteamVR, Virtual Desktop (PC and glasses clients) and a converter like VRidge or ALVR before you begin. Keep the Xreal companion app (for example Ultraxreal or Xreal GlassesControl) available while you test wired and wireless modes.

Step‑by‑step checks you must run now

Run the numbered steps at the end exactly as written. The goal is to confirm whether the feed is true stereoscopic output, a converter-produced stereo, or just a 2D mirror, and then measure latency so you can decide if the result meets your use case.

How to measure latency practically (do this)

Measure end‑to‑end latency with a frame‑trigger test: flash the PC display and record both the PC monitor and the glasses view with a second camera, then count frames between the flash and the glasses image. Add an audio click test and compare audio vs visual timing in the recording.

• Frame‑trigger test: flash white→black on the PC, record both displays, count frames between the source flash and the glasses view.
• Audio check: play a single click while recording to compare audio vs video timing in the glasses.
• Watch for microstutter that lines up with encoder slices (points to encoder overload) versus random packet drops (network).

Per‑app expectations and gotchas

SteamVR can supply native stereo but only if a bridge or driver presents left/right renders to the glasses. If SteamVR appears as a mirrored window inside the client, you have 2D behaviour. Virtual Desktop gives the best low‑latency path for desktop work when set to hardware encoding; if head tracking or frames judder, check encoder and network.

• SteamVR success: two distinct images delivered per frame; test with a scene that renders different content to each eye.
• Virtual Desktop success: smooth head tracking and consistent frame rate with hardware encoder active.
• Converter success: reduced ghosting and tolerable extra latency; doubled edges indicate converter limits.
• Mirroring success: stable 2D image with readable UI and no head‑tracking jitter.

Minimum PC, USB and network config that actually matters

You need a GPU with a hardware encoder (NVENC, AMF or QuickSync). For wired use a USB‑C port that supports DisplayPort Alt Mode or a Thunderbolt/USB4 port; otherwise the glasses fall back to generic USB video. For Wi‑Fi streaming put PC and glasses on the same 5 GHz network and use an uncongested channel.

• Confirm the PC USB‑C port supports DisplayPort Alt Mode or use a Thunderbolt/USB4 port.
• Set the streaming app encoder to hardware (NVENC/AMF/QuickSync) rather than CPU software encoding.
• Place PC on wired Ethernet backhaul and keep the router on an uncongested 5 GHz channel.
• Avoid passive USB‑C hubs; use a direct cable or an active dock that preserves Alt Mode.

Why this fails in practice and the sequence you’ll see

The most common failure is seeing a flat image from SteamVR while assuming you have stereo. That missed stereo check leads to wasted troubleshooting. Another common sequence is encoder overload: high quality settings overwhelm the encoder and cause regular microstutter that matches encoder slices rather than random network drops.

• Symptom: single flat image despite running SteamVR. Cause: bridge did not expose left/right frames.
• Symptom: regular microstutter. Cause: CPU encoder overload.
• Symptom: high Wi‑Fi latency. Cause: congested 5 GHz channel or poor router placement.

Troubleshooting checklist and acceptable fallbacks

Document what you see and keep short clips. If you get stable 2D mirroring with low latency, accept it for productivity. If converter output has ghosting, judge whether it’s tolerable for your apps. If you need true stereoscopic low‑latency gaming and the tests fail, plan hardware changes or choose a different headset.

• Acceptable fallback: smooth 2D mirroring for remote work and media.
• Acceptable fallback: Virtual Desktop with slight compression for non‑competitive gaming.
• Unacceptable: converter stereo with large ghosting or high latency during head motion.

Where to confirm official support and live proof

Check vendor app pages for companion clients and watch short user videos that show the exact feeding mode you tested. See Ultraxreal and Xreal GlassesControl for companion apps, add your clips to GlassesApps, and consult the 10‑minute test flow for a reproducible checklist to share with others.

• See Xreal companion app pages and community clips before you commit.
• Add your test evidence to GlassesApps and link the 10‑minute test for reproducibility: /articles/10-minute-smart-glasses-test.
• Compare behaviour with other XREAL devices at /devices/xreal-air-2-ultra.

Where this usually goes wrong

• You see a single flat image when launching SteamVRSteamVR output is presented as a mirrored desktop window or the bridge is not exposing left/right frames.Check the app output mode, try a different bridge or plugin, and record a short video for comparison with community examples.
• Regular microstutter at short, repeating intervalsCPU software encoder cannot keep up with the chosen resolution or bitrate.Switch to hardware encoder (NVENC/AMF/QuickSync), lower resolution or bitrate, or enable a lower‑latency preset.
• High latency only on Wi‑Fi testsRouter channel congestion, poor placement, or PC not on wired backhaul to the router.Move the router, change to an uncongested 5 GHz channel, or put the PC on wired Ethernet to the router.
• Converter output shows ghosting and doubled edges during motionThe converter synthesizes stereo from a 2D feed and cannot reconstruct accurate parallax for fast head motion.Lower conversion complexity, accept the fallback for static content, or use a workflow that supplies native left/right renders.

The checklist

• Open the Xreal companion apps
• Connect the One Pro+ wired to the PC
• Run desktop mirroring test
• Launch SteamVR and check feed type
• Test Virtual Desktop over Wi‑Fi
• Run a VRidge/ALVR conversion test
• Measure latency with a frame trigger
• Document results and record short clips
• Decide based on acceptable fallbacks

Frequently asked questions