OpenXR 1.1 evolves the standard by incorporating new functionality that was important to the industry but previously not standardized. OpenXR 1.1 evolves the standard by incorporating new functionality that was important to the industry but previously not standardized.
Facilitated by the standards body Khronos Group, OpenXR is a royalty-free standard that aims to standardize the development of VR and AR applications, making for a more interoperable ecosystem. The standard has been in development since April 2017 and over time has become supported by virtually every major hardware, platform, and engine company in the VR industry, including key AR players–but notably, not Apple.
Image courtesy Khronos Group
is the first major update to the standard in more than four and a half years.this week’s release of OpenXR 1.1The update shows the standard evolving as industry needs emerge, an outcome that’s part of the standard’s design.
Built into the framework of OpenXR is the notion of ‘extensions’, which are vendor-specific capabilities which can customize OpenXR’s functionality without needing to first go through the process of being baked into the official standard.
In some cases, such extensions include functionality that eventually becomes universal enough to warrant inclusion in the standard overall. Thus, extensions can be ‘promoted’ and baked into the OpenXR standard for all to use and support.
OpenXR 1.1 sees the inclusion of five capabilities which originally started as extensions:
Local Floor:
provides a new Reference Space with a gravity-aligned world-locked origin for standing-scale content that can be recentered to the current user position at the press of a button without a calibration procedure. The floor height is also estimated. This blog post provides more information about the Local Floor feature and its importance to developers.Stereo With FoveatedRendering:
is a Primary The original vendor extension has been adopted natively by Unity, Unreal and recently NVIDIA Omniverse. It is particularly useful for rendering high-pixel displays that place a heavy burden on GPU The original vendor extension has been adopted natively in Unity, Unreal, and recently by NVIDIA Omniverse.Grip Surface:
provides a Standard Pose Identifier that reliably anchors visual content relative to the user’s physical hand, whether the hand position is tracked directly or inferred from a physical controller’s position and orientation.XrUuid:
provides a Common Data Type to hold a Universally Unique Identifier that follows the IETF RFC 4122.xrLocateSpaces:
provides a Locating Spaces function to improve performance and simplify application code by enabling an application to locate an array of spaces in a single function call populating an “array of structures” (AoS), instead of being limited to locating a single space per function call.Building these extensions directly into OpenXR represents the industry’s consensus on the demand for these features and how they should be implemented across the ecosystem.
OpenXR 1.1 also includes various improvements to existing features and clarifies some capabilities to make the standard clearer for those that want to build implementations that conform to the standard.
Going forward, the OpenXR working group (consisting of representatives from member companies which steer the standard) says it plans to make more regular updates to OpenXR going forward, ensuring that new capabilities continue to be added as industry needs evolve.
“OpenXR 1.1 marks a significant milestone in the development of this open standard that has become widely adopted throughout the XR industry. Alfredo Muniz is the Chair of the OpenXR Working Group. “OpenXR 1.0 was a baseline for new capabilities, and a foundation to experiment with them through extensions.” “Now the Working Group is pivoting to manage regular core specification updates that balance the need for flexibility to ship new functionality with consolidation of proven technology to reduce fragmentation and enable true cross-platform application portability.”