Fact-checked by Grok 2 weeks ago

OpenVR

OpenVR is an open-source application programming interface () and runtime environment developed by , designed to provide developers with a unified way to access (VR) hardware from multiple vendors without requiring knowledge of specific hardware implementations. It serves as the core software layer for SteamVR, enabling cross-compatible VR experiences across devices such as the , , and by abstracting low-level hardware interactions into standardized functions. Released publicly on April 30, 2015, OpenVR marked a significant step in Valve's efforts to foster an open VR ecosystem, initially supporting the Developer Edition alongside SteamVR controllers and base stations for room-scale tracking. At its foundation, OpenVR operates through a layered architecture where applications interact with the runtime via C++ interfaces, allowing seamless integration into game engines like and . Key components include the IVRSystem interface for handling display configuration, head and controller tracking, and input events; the IVRCompositor for managing and frame submission to the headset; and the IVRInput for action-based controller bindings, which support haptic feedback and . Additional interfaces cover chaperone boundaries (IVRChaperone) to prevent real-world collisions, 2D overlays (IVROverlay), and render models (IVRRenderModels) for visualizing hardware components in VR space. This modular design promotes hardware agnosticism, with driver APIs enabling third-party vendors to integrate their devices into the SteamVR runtime. Since its inception, OpenVR has evolved through regular updates, with the stable version 1.0 released in May 2016 to expand developer access to features like integration on the Vive. The SDK is hosted on , with the last major release (version 2.12) issued in August 2023. While has begun integrating support into SteamVR as of 2020 to align with industry standards, OpenVR continues to underpin much of the platform's functionality and remains a foundational tool for development.

Overview

Definition and Purpose

OpenVR is a (SDK) and (API) developed by to facilitate access to (VR) from various vendors. It enables developers to create VR applications without needing in-depth knowledge of specific hardware implementations, serving as a unified interface for interacting with diverse VR systems. The primary purpose of OpenVR is to establish a -agnostic , allowing applications to function across multiple devices without reliance on vendor-specific SDKs. This promotes cross-compatibility and streamlines development by reducing the need for multiple codebases tailored to individual hardware ecosystems. As a result, developers can target a broad range of headsets and peripherals more efficiently, fostering a more inclusive software landscape. At its core, OpenVR's design principle revolves around modular abstraction of essential VR functions, including tracking, input handling, rendering, and display management. These components are exposed through standardized interfaces that encapsulate hardware complexities, enabling seamless integration into applications. The runtime environment for OpenVR is implemented within , Valve's comprehensive platform. This approach emerged in response to the VR fragmentation prevalent in the mid-2010s, when proprietary SDKs—such as the SDK—restricted application portability across competing hardware from different manufacturers. By providing an open, extensible framework, OpenVR addressed these limitations, encouraging broader adoption and interoperability in the burgeoning industry.

Relation to SteamVR

SteamVR is Valve Corporation's comprehensive virtual reality platform, which leverages OpenVR as its foundational and to facilitate interaction with VR hardware from various vendors. This integration allows SteamVR to abstract hardware specifics, enabling seamless support for devices like headsets and controllers without requiring applications to implement vendor-specific code. Within the SteamVR ecosystem, OpenVR primarily manages core hardware interactions, including device enumeration, pose tracking for headsets and controllers, and input routing through standardized interfaces such as IVRSystem and IVRInput. In contrast, SteamVR handles higher-level user-facing elements, such as the compositor for rendering scenes and the for system overlays, ensuring a unified experience across supported hardware. Applications developed using the OpenVR SDK interface directly with the SteamVR runtime, which acts as an intermediary to communicate with OpenVR-compatible drivers installed via Steam. This architecture supports advanced features like room-scale tracking through chaperone boundaries and multi-device configurations, allowing developers to build immersive experiences that scale across different setups. While OpenVR provides the open-source API specification and SDK for broad accessibility, SteamVR encompasses the proprietary runtime environment, driver distribution, and application ecosystem built upon it, distinguishing the two as complementary layers in 's VR framework.

History

Origins and Announcement

The origins of OpenVR trace back to the burgeoning landscape of the mid-2010s, where sought to address the challenges posed by competing ecosystems. In early 2015, Valve entered into a with HTC to develop the headset, announced on March 1, 2015, at the . This collaboration emerged amid a fragmented VR market dominated by development kits (SDKs), such as Oculus VR's SDK for the headset, which had gained prominence following its 2013 crowdfunding success and 2014 developer kit releases. Valve aimed to create a more accessible platform to support emerging VR without tying developers to specific vendors. Central to this effort was the development of OpenVR as a unified API to mitigate vendor lock-in and foster broader ecosystem growth. Internal work at Valve began with early VR prototypes dating back to 2013, evolving through hardware experiments that integrated with the company's Lighthouse tracking system—a laser-based solution for room-scale positional tracking conceptualized around 2014. These prototypes addressed the limitations of existing proprietary systems by prioritizing open-source elements and cross-hardware compatibility, allowing applications to interface with diverse VR devices seamlessly. The motivation stemmed from the need to prevent fragmentation in VR development, where developers faced barriers from closed SDKs that restricted portability across headsets like the Oculus Rift and emerging alternatives. OpenVR was publicly introduced through the release of its SDK on April 30, 2015, via 's platform, positioning it as an for SteamVR applications. This launch followed demonstrations at the Game Developers Conference (GDC) earlier that year, where showcased SteamVR components including , setting the stage for OpenVR's role in enabling hardware-agnostic VR development. engineer Joe Ludwig, a key contributor to the project, elaborated on OpenVR's design in subsequent talks, emphasizing its goal to empower developers with free-to-use APIs that support multiple vendors and promote an open VR ecosystem akin to PC gaming. This release marked a pivotal step in 's vision to accelerate VR adoption by reducing dependencies on proprietary technologies.

Release Timeline and Key Updates

OpenVR's release timeline began with its initial public availability on April 30, 2015, coinciding with the SteamVR beta launch and providing developers with access to VR hardware support for devices like the . The SDK, hosted on since its inception, has fostered community contributions, particularly in developing drivers for diverse hardware. Subsequent updates have focused on enhancing compatibility, performance, and feature sets to support evolving VR ecosystems. Key milestones in OpenVR's evolution include the stable version 1.0 released in May 2016, which established basic (HMD) support, enabling core rendering and input handling, along with access to the on the Vive. Version 1.0.5 in December 2016 introduced initial integration alongside and compositor support, broadening graphics API compatibility for cross-platform development. In August 2022, version 1.26.7 added capabilities through HMD properties. By 2022, version 1.12.5 added support for texture arrays in , enhancing rendering capabilities. in November 2022 brought enhanced event handling and tracker support, including simple tracker integration for improved positional tracking in applications. This update aligned with growing adoption of advanced peripherals. Notable additions during this period included new events and overlay flags for better runtime stability. The most recent major release, version 2.12 in August 2023 (as of November 2025), incorporated support and minimal overlay controls, allowing developers to integrate gaze-based interactions and streamlined UI elements. Additional updates in 2023 emphasized compositor enhancements and driver synchronization with , further optimizing hardware compatibility without deep technical overhauls. These evolutions reflect OpenVR's ongoing role as an open-source foundation for development.
VersionRelease YearKey Features
1.02016Stable release with basic HMD support, initial SteamVR integration, and access
1.122022 texture arrays support, alongside and compositor
2.02022Enhanced events, simple support
2.122023, minimal overlay controls, and SteamVR prop synchronization

Technical Architecture

Core API Interfaces

OpenVR's core API is structured around a set of primary interfaces that enable developers to interact with VR hardware and system components in a vendor-agnostic manner. Implemented in C++ as a library, the consists of pure tables for each interface, allowing applications to request specific versions for . It employs enums such as ETrackedDeviceClass to categorize device types—including HMD, Controller, and GenericTracker—and EVRInitError to report initialization and operational errors. The design favors a single-threaded model for simplicity, with event handling via polling and callbacks to manage interactions without complex synchronization. The IVRSystem interface serves as the foundational module for device management and tracking, providing access to hardware configuration, pose data, and properties for up to 64 tracked devices identified by indices. Developers initialize it through VR_Init, which returns an error code via EVRInitError if issues arise, such as unsupported hardware or driver failures. It leverages to query and differentiate devices, enabling applications to retrieve tracking states, controller poses, and display parameters essential for scene synchronization. IVRInput handles controller and input processing through an action-based system, allowing developers to define custom actions mapped to hardware inputs like buttons and joysticks. To integrate, applications set an action manifest path, obtain handles for action sets, and update states per frame using functions like UpdateActionState, followed by data retrieval via GetDigitalActionData or GetAnalogActionData for digital or analog inputs. This modular approach supports user-configurable bindings via SteamVR's , decoupling input logic from specific device layouts. IVRChaperone manages play area boundaries to enhance safety, defining soft and hard bounds around the tracked . Key methods include GetPlayAreaSize for retrieving the width and depth in meters and GetPlayAreaRect for the full rectangular bounds relative to the tracking origin, with calibration data persisted per tracking environment and updated via events like VREvent_ChaperoneDataHasChanged. IVRRenderModels facilitates loading and rendering of models for devices, such as controllers and headsets, to visually represent in the . It provides functions to enumerate available models by render model names and load their and , ensuring accurate depiction of device geometry sourced from drivers. IVRApplications oversees the application lifecycle, specifying types like VRApplication_Scene for immersive experiences or VRApplication_Overlay for elements during initialization with VR_Init. It handles launching, focusing, and quitting applications, maintaining a of active scenes while supporting background utilities without full access. IVREvents supports polling for and user interactions, integrated primarily through IVRSystem's PollNextEvent method to retrieve events like button presses or tracking changes. This callback-free polling aligns with the API's single-threaded ethos, allowing applications to process queued events in their main loop for responsive interactions.

Compositor and Rendering Pipeline

The IVRCompositor interface in OpenVR serves as the primary mechanism for managing the submission of rendered frames to VR displays, handling essential tasks such as correction to compensate for imperfections in head-mounted displays, and multi-eye rendering to generate separate views for the left and right eyes, ensuring immersive stereoscopic output. This interface abstracts low-level operations, allowing applications to focus on while the compositor applies necessary transformations for accurate . OpenVR's compositor supports multiple graphics backends to accommodate diverse development environments, including 11 and 12 for Windows-based rendering, for cross-platform compatibility, and for high-performance, low-overhead submissions on modern hardware. For texture submission, it accommodates formats such as RGBA8 (e.g., VK_FORMAT_R8G8B8A8_UNORM in ) and supports array textures to efficiently handle stereo rendering by packing left and right eye views into a single resource, reducing API calls and memory overhead. The rendering pipeline in OpenVR follows a structured flow optimized for real-time performance: applications render scenes to offscreen textures representing undistorted eye views, then invoke WaitGetPoses to retrieve predicted head and controller poses for the upcoming frame, enabling low-latency tracking by incorporating motion prediction based on recent sensor data. Following rendering, the Submit function is called for each eye (or using array textures for both), passing the texture handles along with optional bounds to specify the submission region, after which the compositor applies , warping, and for display. This sequence—WaitGetPoses for pose acquisition, rendering to textures, and Submit for finalization—ensures frames align with display refresh cycles, with the compositor fading to a loading grid if submissions are missed for up to 10 frames to maintain user awareness. Advanced features enhance the compositor's robustness and diagnostics: asynchronous reprojection allows the system to interpolate or adjust frames on-the-fly to match variable tracking latencies or display rates, improving smoothness without requiring application-side changes. Frame timing queries via GetFrameTiming provide detailed metrics on submission timing, GPU/CPU loads, and reprojection usage, aiding developers in optimizing performance and identifying bottlenecks. Additionally, overlay support enables the rendering of 2D UI elements directly through the compositor, integrating them seamlessly with 3D content while preserving the VR environment's integrity.

Compatibility and Integration

Supported Hardware

OpenVR, as the core runtime for SteamVR, primarily supports a range of headsets developed in close collaboration with and its partners. The series, including the original , Pro, Pro 2, and Cosmos, are natively compatible through dedicated SteamVR drivers that enable full inside-out and outside-in tracking capabilities. The headset also receives official support, leveraging OpenVR's for high-fidelity audio, finger tracking, and 6 (6DoF) motion with base stations. Additionally, headsets from manufacturers such as , , and are supported via the built-in SteamVR driver, which abstracts hardware-specific details to provide seamless integration without requiring vendor-specific SDKs. For input and tracking peripherals, OpenVR accommodates Valve Index Controllers and HTC Vive Wands, which offer precise 6DoF tracking and haptic feedback when paired with Lighthouse 1.0 or 2.0 base stations. Vive Trackers, including the 3.0 model and the standalone Ultimate Tracker (as of 2024), are fully supported for attaching to objects or the body, enabling full-body tracking in applications that utilize OpenVR's input interfaces. These components rely on the Lighthouse optical tracking system to achieve sub-millimeter accuracy in room-scale environments. Third-party hardware compatibility extends OpenVR's ecosystem through community and vendor-provided drivers. Oculus Rift and Rift S headsets are supported via a Valve-maintained OpenVR driver that interfaces directly with the Oculus runtime, allowing native PC VR experiences. For standalone devices like the series (including , Quest 3, and Quest 3S released in October 2024), wireless streaming solutions such as ALVR emulate SteamVR compatibility, transmitting OpenVR-tracked data over to enable PC VR gaming without wired connections. headsets, such as the Pimax 8KX and , integrate via their proprietary runtime, which is designed to be fully compatible with the OpenVR SDK for high-resolution displays and wide field-of-view tracking. Additional recent supports include the (PC adapter released in 2024 for SteamVR integration), XR Elite (2023, via VIVE Streaming), and HTC Vive Focus Vision (2024, via VIVE Hub for SteamVR). Backward compatibility is maintained for older devices like the original through these drivers, ensuring legacy hardware remains viable. The driver architecture of OpenVR facilitates this multi-vendor support by allowing hardware manufacturers to implement custom drivers as dynamic link libraries (DLLs) that conform to the OpenVR interface specifications, enabling seamless integration without altering the core . This modular approach abstracts low-level hardware details, such as and distortion correction, into vendor-specific modules loaded at runtime.

Software and Engine Support

OpenVR integrates seamlessly with major game engines through dedicated plugins and runtime detection, enabling developers to build VR experiences without deep hardware-specific coding. For , Valve provides the OpenVR XR Plugin, which allows access to SteamVR-compatible hardware via Unity's XR Management system, supporting features like rendering and input handling for devices such as the and . This plugin is particularly useful for projects targeting SteamVR, where Unity's XR Interaction Toolkit can leverage OpenVR for interaction components like grabbing and locomotion. In , the OpenVR plugin facilitates SteamVR integration, allowing developers to enable VR preview and packaging with minimal setup, including support for motion controllers and tracked objects through the engine's VR templates. Additionally, applications built for automatically detect and utilize the OpenVR if SteamVR is installed, streamlining deployment for end-users. OpenVR's operating system support centers on Windows as the primary platform, where it delivers full functionality through the SteamVR runtime, including high-performance rendering and low-latency input. compatibility is available via SteamVR, enabling VR development and runtime execution on distributions like , though it requires additional setup for drivers and Proton for non-native applications. Support for macOS was deprecated in 2020, with ceasing updates to focus resources on Windows and , rendering OpenVR non-functional on modern macOS versions without unofficial workarounds. Development tools for OpenVR include the SteamVR SDK, which provides samples, utilities, and testing environments for validating VR interactions and performance within Steam's ecosystem. The OpenVR Advanced Settings tool offers users granular control over configurations like chaperone boundaries and , accessible as a SteamVR overlay for runtime adjustments. For scripting and prototyping, community-maintained bindings such as enable integration, allowing developers to interface with OpenVR APIs for tasks like pose tracking and event handling without compiling C++ code. To install and use OpenVR, developers must have installed along with the SteamVR runtime, which handles the core OpenVR and driver management. The OpenVR SDK itself is freely downloadable from , offering standalone access for non-Steam applications, including headers, samples, and build instructions for custom integrations. This setup abstracts hardware details, allowing applications to query and utilize any compatible device through a unified interface.

Adoption and Evolution

Usage in Gaming and Applications

OpenVR has been extensively utilized in gaming to deliver immersive virtual reality experiences, particularly through its integration with SteamVR. Notable titles such as Half-Life: Alyx leverage OpenVR to enable precise 6 degrees of freedom (6DoF) interactions, allowing players to manipulate objects and navigate environments with natural hand tracking and motion controls. Similarly, rhythm game Beat Saber employs OpenVR for responsive saber-swinging mechanics that respond to full-body movements, enhancing rhythmic immersion across compatible headsets. Physics-based adventure Boneworks further demonstrates OpenVR's capabilities by simulating realistic body interactions and environmental physics, where players use their virtual limbs to solve puzzles and combat enemies in a fully interactive world. Beyond gaming, OpenVR powers a variety of non-gaming applications, including simulations and enterprise solutions. In flight simulation, Digital Combat Simulator (DCS) World integrates OpenVR via SteamVR to provide cockpit views and 6DoF head tracking, enabling realistic pilot training scenarios without requiring additional middleware. Social VR platform VRChat relies on an OpenVR backend for multiplayer interactions, supporting avatar animations, gesture recognition, and spatial audio in user-generated worlds. In enterprise contexts, OpenVR facilitates training applications, such as industrial safety simulations where workers practice hazardous procedures in controlled virtual environments, as seen in custom VR setups for manufacturing and operations. Adoption of OpenVR has grown significantly, with hosting over 6,700 VR titles compatible via SteamVR as of late 2025, spanning , simulations, and tools. This ecosystem fosters vibrant modding communities that extend OpenVR's reach, including custom drivers for non-standard hardware like DIY headsets and controllers, allowing enthusiasts to adapt experiences to unique setups. In practice, OpenVR's abstracted simplifies porting content across diverse headsets, such as , , and , thereby reducing development time for multi-platform titles by minimizing hardware-specific optimizations. While trends toward standards like are emerging for broader compatibility, OpenVR remains a cornerstone for current PC deployments.

Transition to OpenXR and Future Outlook

As the virtual reality (VR) and augmented reality (AR) industries matured, the Khronos Group released OpenXR 1.0 on July 29, 2019, establishing an open, royalty-free standard designed to unify cross-platform development and supersede proprietary APIs like OpenVR for broader hardware compatibility. OpenXR's layered architecture allows applications to target a single API while enabling runtime-specific extensions, addressing OpenVR's limitations in supporting non-Steam ecosystems such as Meta Quest or Microsoft HoloLens. In response, Valve integrated OpenXR runtime support into SteamVR starting with version 1.14 in beta during late 2020, followed by full implementation in version 1.16.8 by February 2021, allowing developers to leverage OpenXR while maintaining backward compatibility. Despite the shift, OpenVR retains a vital legacy role within the Steam ecosystem, where it continues to power a vast of existing applications and hardware integrations without planned immediate discontinuation. deployment models have emerged, enabling OpenVR-targeted apps to operate through layers or compatibility tools like OpenComposite, which translate OpenVR calls to native OpenXR for reduced dependency on SteamVR. This approach preserves access to Steam's controller bindings and overlay features while facilitating migration to more portable runtimes. Transitioning fully presents challenges, including performance overhead when using SteamVR as an runtime compared to native implementations, as identified in analyses of headsets where direct OpenXR paths yield higher frame rates and lower latency. Broader adoption by 2025 has heightened risks for OpenVR, with major engines like 5.4 explicitly phasing it out in favor of OpenXR to streamline development across platforms. Similarly, Meta's of proprietary APIs announced in July 2021 underscores the industry's pivot, potentially isolating OpenVR-dependent projects from future hardware advancements. Looking ahead, may extend OpenVR through updates enhancing and integration, aligning with their ongoing development of next-generation XR hardware like the announced Steam Frame headset (previously codenamed Deckard), which is set for release in 2026 and emphasizes cross-standard support including . In November 2025, announced the Steam Frame VR headset, a standalone device set for 2026 release, which is expected to support and potentially leverage OpenVR for VR compatibility. Community-driven efforts, such as custom drivers on for trackers like SlimeVR or revived support via the Oasis driver, ensure sustained compatibility for niche hardware amid 's dominance. These initiatives highlight OpenVR's enduring utility in specialized scenarios, even as the ecosystem evolves toward unified standards.

References

  1. [1]
    ValveSoftware/openvr: OpenVR SDK - GitHub
    OpenVR is an API and runtime that allows access to VR hardware from multiple vendors without requiring that applications have specific knowledge of the ...API Documentation · Releases · ValveSoftware/openvr Wiki · Driver Documentation
  2. [2]
    OpenVR SDK Now Available - Steam News - SteamVR
    Applications are now able to access SteamVR hardware using the new OpenVR SDK. The SDK is available for download here. It provides support for the HTC Vive ...
  3. [3]
    Valve Releases OpenVR SDK - Phoronix
    Apr 30, 2015 · Valve Software today released the OpenVR SDK, an API and runtime that allows accessing virtual reality hardware from multiple vendors without ...
  4. [4]
    API Documentation · ValveSoftware/openvr Wiki - GitHub
    Oct 18, 2020 · The OpenVR API provides a game with a way to interact with Virtual Reality displays without relying on a specific hardware vendor's SDK.
  5. [5]
    Releases · ValveSoftware/openvr - GitHub
    OpenVR SDK 2.12. Aug 19 · v2.12.14 ; OpenVR SDK 2.5.1. Mar 26, 2024 · v2.5.1 ; v2.2.3. Jan 19, 2024 · v2.2.3 ; OpenVR SDK 2.0.10. Nov 7, 2023 · v2.0.10 ; OpenVR SDK ...Missing: history | Show results with:history
  6. [6]
    Valve moves on from OpenVR, goes all-in with OpenXR for SteamVR
    Jun 25, 2020 · Recently, Valve released a new SteamVR Beta that was aimed at developers with initial support for the OpenXR specification and it appears ...
  7. [7]
    Making Valve's OpenVR Truly Inclusive for VR Headsets
    Jul 20, 2015 · In this guest article, a veteran developer who goes by the name of 'Phr00t' shares his recent significant advancements using Valve's OpenVR, ...
  8. [8]
    OpenVR (Steamworks Documentation)
    OpenVR is an API and runtime that allows access to VR hardware from multiple vendors without requiring that applications have specific knowledge of the hardware ...
  9. [9]
    SteamVR - Valve Developer Community
    Sep 17, 2025 · SteamVR is a suite of tools and services for VR including OpenVR, Chaperone, Compositor, Lighthouse Tracking, and more.
  10. [10]
    HTC Partners With Valve for Vive Virtual Reality Headset | TIME
    Mar 1, 2015 · HTC on Sunday announced the HTC Vive, a joint HTC-Valve virtual reality headset that's due out by the end of the year.Missing: origins | Show results with:origins
  11. [11]
  12. [12]
    Three years of Valve prototype VR hardware | PC Gamer
    Mar 10, 2015 · Here's a look at Valve's VR development timeline, from rough prototypes to the headset we tried on during GDC.
  13. [13]
    Valve's Lighthouse Base Station in Action, Inner Workings Explained
    May 18, 2015 · Some of the inner workings of Valve's Lighthouse base station, an infrared laser-emitting device used for 'room scale' positional tracking, were revealed today.
  14. [14]
    News - Valve Announces Link, Source 2, SteamVR, And More At GDC
    Mar 4, 2015 · "Now that we have Lighthouse, we have an important piece of the puzzle for tackling VR input devices," said Valve's Joe Ludwig. "The work on ...Missing: OpenVR | Show results with:OpenVR
  15. [15]
    Valve's Joe Ludwig to Talk 'OpenVR' and 'Lighthouse' Hardware ...
    Apr 29, 2015 · The 20 minute talk, entitled “OpenVR and You,” will center on Ludwig's work with OpenVR, and what the free-to-use VR APIs have to offer potential app ...Missing: GDC | Show results with:GDC
  16. [16]
  17. [17]
  18. [18]
    IVRSystem_Overview · ValveSoftware/openvr Wiki - GitHub
    The vr::IVRSystem interface provides access to display configuration information, tracking data, distortion functions, controller state, events, and device ...Missing: IVRInput | Show results with:IVRInput<|control11|><|separator|>
  19. [19]
    SteamVR Input · ValveSoftware/openvr Wiki - GitHub
    Nov 20, 2018 · To use the IVRInput API in an application, a developer should take the following steps: Check "Enable debugging options in the input binding ...Missing: core | Show results with:core
  20. [20]
    IVRChaperone_Overview
    ### Summary of IVRChaperone Interface: Purpose for Play Area Boundaries
  21. [21]
    IVRRenderModels_Overview · ValveSoftware/openvr Wiki - GitHub
    Aug 17, 2015 · The vr::IVRRenderModels interface provides access to 3D models related to the attached hardware. Wherever possible these models reflect the ...
  22. [22]
    IVRCompositor_Overview · ValveSoftware/openvr Wiki - GitHub
    The Compositor simplifies the process of displaying images to the user by taking care of distortion, prediction, synchronization and other subtle issues.
  23. [23]
    DirectX12 · ValveSoftware/openvr Wiki - GitHub
    The command list is submitted to the queue using ExecuteCommandLists; The left eye texture is submitted using IVRCompositor::Submit. The right eye texture is ...
  24. [24]
    Vulkan · ValveSoftware/openvr Wiki - GitHub
    A simple example of using Vulkan with SteamVR on Windows/Linux can be found in the SDK https://github.com/ValveSoftware/openvr/tree/master/samples/ ...Missing: v1. | Show results with:v1.
  25. [25]
    IVRCompositor::Submit · ValveSoftware/openvr Wiki - GitHub
    Feb 25, 2018 · Updated scene texture to display. If pBounds is NULL the entire texture will be used. OpenGL dirty state: glBindTexture virtual EVRCompositorErrorMissing: interface | Show results with:interface
  26. [26]
    How to use Submit_GlArrayTexture · Issue #1590 - GitHub
    Sep 17, 2021 · I noticed Submit_GlArrayTexture was added an EVRSubmitFlags for compositor Submit. There doesn't seem to be any documentation on how to use it.Missing: formats RGBA8 stereo
  27. [27]
  28. [28]
    Driver Documentation · ValveSoftware/openvr Wiki - GitHub
    Apr 18, 2022 · It is advisable to use the built-in SteamVR drivers as references. For example, the Oculus driver is maintained by Valve and demonstrates nearly ...Missing: hardware | Show results with:hardware
  29. [29]
    The JSON File (Lighthouse Devices) · ValveSoftware/openvr Wiki
    Aug 1, 2022 · This document describes all of the variables that may be stored in the JSON file, what they mean, and how to specify them.
  30. [30]
    Unity: Getting Data from VIVE Tracker (SteamVR) | VIVE OpenXR
    By following this guide, you can retrieve the tracking data of VIVE Tracker connected to SteamVR within the XR_HTCX_vive_tracker_interaction extension.
  31. [31]
    alvr-org/ALVR: Stream VR games from your PC to your ... - GitHub
    * ALVR for Quest 1 is not available through the Meta store. ** Works on some ... ALVR and SteamVR for the best performance and compatibility. (NVIDIA ...Installation guide · ALVR · Issues · Pull requests 24
  32. [32]
    FAQ - Pimax Developer Center
    Does Pimax PC VR devices(5K/8K/etc) support OpenXR SDK? Yes. The Pimax PC VR runtime is compatiable with OpenVR SDK, since OpenVR has fully supported OpenXR 1.0 ...
  33. [33]
    OpenVR plugin for Unity's XR API - GitHub
    The OpenVR XR Plugin gives you access to rendering on all major VR devices through one interface. Explicit support for: HTC Vive, HTC Vive Cosmos, Oculus Rift, ...
  34. [34]
    Developing for SteamVR in Unreal Engine - Epic Games Developers
    This page describes how SteamVR is supported in Unreal Engine, and how to set up your environment to develop with SteamVR.
  35. [35]
    Actions · ValveSoftware/openvr - GitHub
    Linux, macOS, Windows, ARM, and containers. Hosted runners for every major OS make it easy to build and test all your projects.
  36. [36]
    Valve drops VR support for macOS - TechCrunch
    May 1, 2020 · Valve is calling it quits on macOS support for its virtual reality platform. A Valve employee posted an update to the company's SteamVR forums.
  37. [37]
    OpenVR Advanced Settings Dashboard Overlay - GitHub
    To upgrade an existing installation first stop SteamVR and delete the old application folder (or override it). Then start SteamVR and run AdvancedSettings.exe ...
  38. [38]
    cmbruns/pyopenvr: Unofficial python bindings for Valve's OpenVR ...
    Unofficial python bindings for Valve's OpenVR virtual reality SDK, located at https://github.com/ValveSoftware/openvrMissing: tools | Show results with:tools
  39. [39]
    Best PC VR Games: 25 Titles On Steam And Oculus - Summer 2025
    Sep 1, 2025 · Half-Life: Alyx is arguably the best PC VR game yet, and we hope to see more from Valve. Platforms: Steam · Half-Life: Alyx Review - Supremely ...
  40. [40]
    VR - DCS World
    To work in VR mode in DCS World, you need to download and install two free programs from Steam. The first launch of SteamVR will enable a VR gaming headset.
  41. [41]
    OpenVR FSR Support - General Discussion - VRChat Ask Forum
    Jul 19, 2024 · A little while ago, I wanna say pre-EAC patch, there was a lovely mod that allowed the playerbase to use AMD's FSR features with the game.Missing: applications simulations DCS enterprise training
  42. [42]
    Strivr: Elevate workforce performance with the power of XR
    Strivr gives enterprise teams the power to elevate workforce engagement, performance, and productivity at scale through AI-backed immersive learning experiences ...Careers · Strivr Partner Program · Contact us · Platform<|separator|>
  43. [43]
    Steam Game Releases Summary for VR - SteamDB
    363 VR games have been released in 2025 on Steam (cumulative: 6758). · 537 VR games have been released in 2024 on Steam (cumulative: 6395). · 625 VR games have ...
  44. [44]
    sencercoltu/openvr-customhmd - GitHub
    DIY attempt for building OpenVR compatible HMD and controllers, and drivers (Windows only). I started my VR experience with a custom built HMD by using ...
  45. [45]
    Just how “open” is the future of PC virtual reality? - Ars Technica
    Jul 15, 2015 · Valve, on the other hand, is building a more open platform that it says will support multiple headsets from multiple makers, all of which run on ...
  46. [46]
    OpenXR - High-performance access to AR and VR
    OpenXR is a royalty-free, open standard that provides a common set of APIs for developing XR applications that run across a wide range of AR and VR devices.Missing: OpenVR porting
  47. [47]
    SteamVR Update Adds Full OpenXR Support - UploadVR
    Feb 24, 2021 · Valve announced the latest version of SteamVR, 1.16.8, now has full OpenXR support. OpenXR is a new standard that provides an API for VR and AR ...
  48. [48]
    SteamVR :: Transitioning To OpenXR - Steam Community
    First, it does not mean that OpenVR support is going away. OpenVR applications will continue to work not just on hardware that exists today, but also on the ...
  49. [49]
  50. [50]
    Oculus All In on OpenXR: Deprecates Proprietary APIs
    Apr 15, 2024 · OpenXR will enter Full Support and will be the preferred API for all new applications going forward, including those that plan to use Passthrough Experimental ...Missing: risks | Show results with:risks
  51. [51]
    Is a New Valve XR Headset in Development? - XR Today
    Nov 14, 2023 · Valve's USPTO request highlighted how Deckard would support mixed and augmented reality (MR/AR) functions via integrated hardware that ...Missing: OpenVR | Show results with:OpenVR
  52. [52]
    SlimeVR driver for OpenVR - GitHub
    SlimeVR driver for OpenVR. Used to communicate between the SlimeVR server and SteamVR. How to get It's recommended to install the driver via the SlimeVR ...