Repository navigation
Compatibility
VRViewer compatibility depends on the application's available capture sources, the VR runtime, and the rendering path used by the software being viewed.
This page describes how to evaluate compatibility and report configurations that work or fail.
| Component | Requirement |
|---|---|
| Operating System | Windows 10 or Windows 11 (64-bit) |
| Processor | 2-core CPU or better |
| Memory | 4 GB RAM |
| Graphics | GPU supporting the graphics APIs required by the selected source |
| Supported Sources | SteamVR and OpenXR runtimes |
| OpenXR Graphics APIs | Direct3D 11 (D3D11), Direct3D 12 (D3D12) |
| Storage | 5 GB of free disk space |
| Internet | Required for online license validation, updates, and downloads, where applicable |
VRViewer supports stereoscopic headsets using a conventional two-view layout (left and right eye). Quad-view rendering configurations are not supported.
- Easy Anti-Cheat (EAC): Currently supported.
- BattlEye: Not supported when using the OpenXR capture source.
Anti-cheat compatibility may vary by game, capture source, and anti-cheat configuration. Support for one anti-cheat system does not guarantee compatibility with every game using it.
These are baseline recommendations, not guaranteed minimums. Windows 10 was tested in a virtual machine with 2 vCPUs and 2 GB RAM for installation and the UI/Test source only. OpenXR and SteamVR capture requirements have not yet been validated under these resource constraints. Hardware and runtime compatibility may vary.
A headset working with its normal VR software does not, by itself, guarantee compatibility with every VRViewer source.
When reporting a headset-related issue, include:
- Headset manufacturer and model
- VR runtime being used
- VRViewer version
- Whether the headset and target VR application work normally without VRViewer
Compatibility should be recorded based on testing with a specific configuration.
OpenXR is an API used by VR applications to communicate with an OpenXR runtime.
For OpenXR-related issues, identify:
- The active OpenXR runtime
- The runtime version, if known
- The headset in use
- The target application
- Whether the problem occurs with one application or multiple applications
Applications may use different graphics APIs and rendering configurations. Support for OpenXR does not necessarily mean that every application's rendering path can be captured.
SteamVR-related behavior can depend on the SteamVR installation, the active VR session, and the target application's configuration.
When reporting a SteamVR source problem, include the SteamVR version, headset, target application, and any error messages shown by VRViewer or SteamVR.
VRViewer may provide multiple sources, such as OpenXR, SteamVR, and a test source, depending on the version.
A test source can help distinguish problems with the viewer itself from problems associated with a live capture source.
The presence of a source in the application does not guarantee that every application or graphics configuration is supported.
VR applications may render through different graphics APIs. Compatibility with a runtime does not automatically establish compatibility with every graphics API or rendering path.
If you encounter a capture issue, include the target application's name and any known information about its graphics API.
Do not assume that a game supports a particular capture path solely because it supports VR.
Only configurations that have been tested should be listed as confirmed compatible.
Use the following information when documenting a test:
| Field | Information to record |
|---|---|
| VRViewer version | Exact application version |
| Headset | Manufacturer and model |
| Runtime | OpenXR runtime or SteamVR version |
| Target application | Application being viewed |
| Graphics API | If known |
| Capture source | Source selected in VRViewer |
| Result | Working, partially working, or not working |
| Notes | Limitations, errors, or special setup requirements |
An untested configuration should be marked Not yet tested, rather than assumed compatible or incompatible.
If your configuration does not work:
- Verify that the target VR application works normally.
- Confirm which source is selected in VRViewer.
- Record your headset, runtime, and application versions.
- Note any error messages and steps that reproduce the issue.
- Submit a bug report.
See Troubleshooting for additional guidance.