Skip to content

Releases: KhronosGroup/OpenXR-Docs

OpenXR Specification (Source) 1.1.38

10 Jun 22:07
release-1.1.38
Compare
Choose a tag to compare

OpenXR Specification 1.1.38 (2024-06-09)

This is a fairly small release, with one new extension and a handful of fixes.

  • Registry
    • Addition: New multi-vendor extension: XR_EXT_composition_layer_inverted_alpha
      (internal MR 3085,
      internal MR 3385)
    • Chore: Reserve an extension for Logitech.
      (internal MR 3384)
    • Chore: Register author tag for Deep Mirror.
      (OpenXR-Docs PR 171)
    • Fix: XrCompositionLayerPassthroughFB has a "parentstruct" of
      XrCompositionLayerBaseHeader (it is based on this type), rather than
      "structextends" (in the next chain). Bump extension revision.
      (internal MR 3305)
    • Fix: XR_EXT_plane_detection: Fix extents description and plane axis to match
      CTS and implementations.
      (internal MR 3374,
      internal issue 2281)
    • Fix: Correct typo in XR_FB_keyboard_tracking flag description.
      (internal MR 3393)
  • Specification
    • Addition: New multi-vendor extension specification:
      XR_EXT_composition_layer_inverted_alpha
      (internal MR 3085)
    • Addition: Support emitting more comment attributes/elements from XML, and
      enable it for standalone headers.
      (internal MR 3377)
    • Fix: Note errata regarding third field name in
      XrCompositionLayerPassthroughFB. Bump extension revision due to XML fix.
      (internal MR 3305)
    • Fix: XR_EXT_plane_detection: Fix extents description and plane axis to match
      CTS and implementations.
      (internal MR 3374,
      internal issue 2281)
    • Fix: Correct typo in XR_FB_keyboard_tracking flag description.
      (internal MR 3393)
    • Fix: Correct typo in loader design document.
      (internal MR 3393)

OpenXR Specification (Source) 1.1.37

25 May 02:25
release-1.1.37
Compare
Choose a tag to compare

OpenXR Specification 1.1.37 (2024-05-23)

This release adds new defines for easier use of both OpenXR 1.0 and 1.1 with
up-to-date headers, as well as some minor fixes, cleanups, and clarifications.

OpenXR Specification (Source) 1.1.36

15 Apr 05:42
release-1.1.36
Compare
Choose a tag to compare

OpenXR Specification 1.1.36 (2024-04-15)

This is a substantial update to the OpenXR specification.

Read more

OpenXR Specification (Source) 1.0.34

17 Feb 20:58
release-1.0.34
Compare
Choose a tag to compare

OpenXR Specification 1.0.34 (2024-02-16)

This release features clarifications to the specification, as well as a number
of new multi-vendor and vendor extensions, and additional functionality in the
reflection header.

  • Registry
  • Specification
    • Clarification: Change normative "should" statements to "may" for the
      interaction of user engagement sensors and the session lifecycle, in order to
      represent the intended and actual optionality of that behavior. Specifically,
      it is valid but completely optional for runtimes to use the user engagement
      sensor (if it exists) to move to XR_SESSION_STATE_STOPPING.
      (internal MR 3022)
    • Clarification: Swapchain usage flags errors should return
      XR_ERROR_FEATURE_UNSUPPORTED as well.
      (internal MR 3194)
    • New multi-vendor extension specification: XR_EXT_user_presence
      (internal MR 2706,
      internal issue 1585)
    • New vendor extension specification: XR_META_recommended_layer_resolution
      (internal MR 2570)
    • New vendor extension specification: XR_META_automatic_layer_filter
      (internal MR 2696)
    • New vendor extension specification: XR_META_spatial_entity_mesh
      (internal MR 2773)
    • New vendor extension specification: XR_FB_face_tracking2
      (internal MR 2811)
    • New vendor extension specification: XR_VARJO_xr4_controller_interaction
      (internal MR 3078)
    • Spec: Move originals of images to separate folder.
      (internal MR 3218)
    • Spec: Fix issue where some comments before defines were missing a newline.
      (internal MR 3227)
    • Style guide: Fix several leftover references to Vk/Vulkan.
      (internal MR 2967)
    • XR_FB_scene: Update to spec version 4.
      (internal MR 2774)
    • XR_META_headset_id and XR_FB_spatial_entity: Bump spec versions to drop
      XR_EXT_uuid dependency from spec.
      (internal MR 2577)
    • external: Update Jinja2 Python module shipped with repository (for spec/header
      generation) to 2.11.3.
      (internal MR 3221,
      internal MR 3237)

OpenXR Specification (Source) 1.0.33

04 Jan 23:31
release-1.0.33
Compare
Choose a tag to compare

OpenXR Specification 1.0.33 (2024-01-03)

This release primarily adds new ratified functionality to the specification
describing the loader interaction with runtimes and API layers. This
functionality was previously described in non-normative text in the loader
design document, but was universally adopted for compatibility. It is now part
of the normative, ratified core specification. This change only affects vendors
of runtimes and API layers as well as contributors to the OpenXR loader:
applications do not directly use this API, the loader uses it on their behalf. A
number of other small fixes are also included.

  • Registry
    • Extension reservation: Update author ID and reserve extensions for Varjo.
      (internal MR 3083)
    • Extension reservation: Reserve 10 extension ids each for ANDROIDX &
      ANDROIDSYS.
      (internal MR 3086)
    • Khronos ratified addition: Specify the existing loader negotiation functions
      (without modification) in the XML, moving from loader_interfaces.h to a new
      generated header openxr_loader_negotiation.h.
      (internal MR 2807,
      internal issue 1953)
    • XR_KHR_android_thread_settings: Fix the description of
      XrAndroidThreadTypeKHR enum values - they were swapped relative to their
      implicit meaning from their name.
      (internal MR 3077)
    • XR_MNDX_egl_enable: Update version to 2 to reflect function pointer type
      change released in 1.0.29.
      (OpenXR-Docs PR 159)
  • Specification
    • Khronos ratified specification addition: move loader negotiation functions into
      the specification proper (from the loader design doc), moving corresponding
      functions from loader_interfaces.h to openxr_loader_negotiation.h. (The
      exact ratified core specification text is 1.0.29 with these changes added,
      available internally. Non-substantive core specification updates/fixes have
      occurred since then.)
      (internal MR 2807,
      internal issue 1953,
      internal MR 3101)
    • Scripts: Adjust Makefile so we now error on any checkSpecLinks warning when
      running that target.
      (internal MR 3072)
    • XR_HTC_anchor: Fix parameter name error in prose description.
      (internal MR 3072)
    • XR_KHR_android_thread_settings: Fix the description of
      XrAndroidThreadTypeKHR enum values - they were swapped relative to their
      implicit meaning from their name.
      (internal MR 3077)
    • XR_MNDX_egl_enable: Update revision info and version to 2 to reflect function
      pointer type change released in 1.0.29.
      (OpenXR-Docs PR 159)
    • loader design doc: Fix minor typos.
      (internal MR 3065,
      internal MR 3103)
  • Misc
    • Update/correct names.
    • Ship a .mailmap file in the public repositories, maintained separately
      from the larger one used in the private monorepo, to correct names/emails
      and unify contributor identities.
    • Update Khronos Group copyright dates.

GitOrigin-RevId: a561c5898b72f59965790790a28bbc3b7e9bcf13

OpenXR Specification (Source) 1.0.32

29 Nov 22:00
release-1.0.32
Compare
Choose a tag to compare

OpenXR Specification 1.0.32 (2023-11-29)

This release contains a number of vendor extensions, plus a new ratified
revision to the XR_KHR_loader_init extension that specifies forwarding the
init calls to API layers. Vendors of API layers, primarily on Android, must
verify they can handle being passed XR_NULL_HANDLE for the instance parameter
of xrGetInstanceProcAddr, to avoid bugs when using the updated loader. This
release also features the remaining "checkSpecLinks" consistency warning fixes
in the manually-written specification text in extensions.

  • Registry
  • Specification
    • XR_KHR_loader_init: New Khronos ratified revision, now additionally specifies
      forwarding loader init calls to API layers
      (internal MR 2703)
    • Fix "checkSpecLinks" warnings about member and parameter references in
      extensions to the specification. This has changed the documentation of a number
      of structures and functions across several extensions, although the C
      prototypes/definitions in the spec as well as the header file contents have
      stayed constant.
      (internal MR 2970)
    • New vendor extension specification: XR_HTC_anchor
      (internal MR 2667)
    • New vendor extension specification: XR_META_touch_controller_plus
      (internal MR 2702)
    • New vendor extension specification: XR_ML_marker_understanding
      (internal MR 2750)
    • New vendor extension specification: XR_ML_localization_map
      (internal MR 2802,
      internal MR 3045,
      internal MR 3047)

GitOrigin-RevId: 0a6bbc30cf10fdec436dfa81abf27747251a0821

OpenXR Specification (Source) 1.0.31

19 Oct 16:18
release-1.0.31
Compare
Choose a tag to compare

OpenXR Specification 1.0.31 (2023-10-18)

This release features two new vendor extensions, some XML revisions to other
vendor extensions, and a substantial amount of fixes to the prose of the core
specification and some extensions. All specially-formatted mentions of a
parameter or field name (that is, names marked up with the pname macro in the
AsciiDoctor source) are now being checked by a script to be sure they are known.
With the fixes in this release, nearly all such name mentions now either (1)
match the function or structure in whose description they are mentioned, or (2)
have been qualified with the function or structure to which they do belong.
Misspellings, missing fields/parameters, and extraneous parameters have been
fixed as well. (Some fixes of this type to vendor extensions are still pending
and will be in an upcoming patch release.) While this has changed the prose, it
has not resulted in substantive changes to the XML, and therefore the code
snippets in the specification as well as the header files remain accurate and
unaffected by these fixes.

GitOrigin-RevId: 38114c3ba8eb46d6fafe1761ed08e263ce132237

OpenXR Specification (Source) 1.0.30

20 Sep 16:35
release-1.0.30
Compare
Choose a tag to compare

OpenXR Specification 1.0.30 (2023-09-20)

This release is primarily a quality improvement release, fixing a range of
issues in the registry and specification, in addition to a new vendor extension
and an updated vendor extension.

  • Registry
  • Specification
    • Clarify how prior frame state is reset when a session starts running.
      (internal MR 2759,
      internal issue 2029)
    • Clean up normative language in FB vendor extensions.
      (internal MR 2563)
    • Clean up normative language in the Rendering chapter.
      (internal MR 2801)
    • Fix formatting and markup errors in the loader design document.
      (internal MR 2866)
    • Fix generated broken links from valid usage in ref pages to the next chain
      fundamentals.
      (internal MR 2931,
      internal issue 1369)
    • Fix broken links and update URLs in specification, extension process, style
      guide, and loader doc.
      (internal MR 2935)
    • New vendor extension specification: XR_YVR_controller_interaction
      (internal MR 2841)
    • XR_BD_controller_interaction: Add support for G3 devices
      (internal MR 2872)
    • XR_EXT_debug_utils: Fix XML to reflect that
      XrDebugUtilsMessengerCallbackDataEXT parameters messageId and
      functionName are optional.
      (internal MR 2864)
    • scripts: Fix member name lookups in entity_db, enabling numerous spec
      warnings that had been hidden.
      (internal MR 2923)
    • Fix specification errors (core and extension) highlighted by fixed tooling.
      (internal MR 2923)

GitOrigin-RevId: f7a0c0f3691f0c7b0a239cb34e41d01042d5a02a

OpenXR Specification (Source) 1.0.29

25 Aug 22:04
release-1.0.29
Compare
Choose a tag to compare

OpenXR Specification 1.0.29 (2023-08-25)

This release contains several fixes to the specification, as well as
enhancements to the loader documentation/specification to support architecture
and ABI specific active runtime manifest names on Linux and Android.

  • Registry
    • Change PFNEGLGETPROCADDRESSPROC (for eglGetProcAddress) to a locally
      defined type to avoid compiler errors.
      (internal MR 2468)
    • Extension reservation: Register author ID and reserve vendor extensions for
      YVR.
      (internal MR 2832)
    • New vendor extension: XR_META_passthrough_preferences
      (internal MR 2694)
    • XR_HTCX_vive_tracker_interaction: Added new role paths for wrists and ankles.
      (internal MR 2728)
  • Specification
    • Change PFNEGLGETPROCADDRESSPROC (for eglGetProcAddress) to a locally
      defined type to avoid compiler errors.
      (internal MR 2468)
    • Fix specification text mentions of eyeVisibility field in Khronos composition
      layer extensions, to match the XML and headers.
      (internal MR 2878)
    • Improvement: Add note to OpenXR styleguide to discourage use of callback
      functions in OpenXR extensions.
      (internal MR 2734)
    • Loader spec: Clarify and deduplicate the loader specification's listing of
      android manifest search paths.
      (internal MR 2829,
      internal issue 2046)
    • Loader spec: Fix description of <queries> element contents: existing
      description would fail to install.
      (internal MR 2840,
      internal issue 2053)
    • Makefile: Remove obsolete cygwin support in spec building target, no longer
      needed and actually caused it to not work under MSYS2.
      (internal MR 2885)
    • New vendor extension specification: XR_META_passthrough_preferences
      (internal MR 2694)
    • Style guide: Document the XML schema of xr.xml
      (internal MR 2875)
    • XR_HTCX_vive_tracker_interaction: Added new role paths for wrists and ankles.
      (internal MR 2728)
    • XR_OPPO_controller_interaction: Fix formatting of path lists.
      (internal MR 2831,
      OpenXR-Docs issue 156,
      internal issue 2047)
    • scripts: Provide better feedback on interface struct erroneously having a
      values attribute.
      (internal MR 2856)
    • scripts: Update regex in xrconventions to allow words in type naming that
      succeed digits but start with a "D"
      (internal MR 2857)
    • scripts: Fix formatting of "basetype" (generally typedef) names to once again
      be monospace "code".
      (internal MR 2890,
      internal issue 2048)

OpenXR Specification (Source) 1.0.28

10 Jul 22:37
release-1.0.28
Compare
Choose a tag to compare

OpenXR Specification 1.0.28 (2023-07-10)

This release features a number of new extensions, including several multi-vendor
extensions, among other improvements and clarifications.

  • Registry
  • Specification
    • Added normative language clarifying that XrViewConfigurationType usage must
      be 'activated' by xrBeginSession (or by extensions). This was previously
      described clearly but non-normatively.
      (internal MR 2700)
    • Clarify the behavior of functions which initiate an asynchronous request when
      the function fails immediately.
      (internal MR 2716)
    • Clarify that we do intend to capture most invalid usage with return codes,
      unlike Vulkan, which is where we borrowed some of this language from.
      (internal MR 2762)
    • Corrected the extension enum base to 10^9.
      (internal MR 2693,
      OpenXR-Docs issue 148,
      internal issue 1979)
    • Fix nesting level of "Valid Usage" sections and headings, which resulted in a
      re-numbering of sections between 2.7 and 3.
      (internal MR 2761,
      OpenXR-Docs issue 149,
      internal issue 1989)
    • Fix nesting level of some sections and headings in the Rendering chapter, which
      resulted in a re-numbering of sections between 10.4 and 11.
      (internal MR 2761,
      OpenXR-Docs issue 149,
      internal issue 1989)
    • Fix flags-type boilerplate to mention XrCompositionLayerFlagBits in the body
      of the ref page of XrCompositionLayerFlags for a more usable ref page
      experience.
      (internal MR 2813)
    • Fix markup of a subpathname: which was marked as a pathname:.
      (internal MR 2673)
    • Loader docs: Specify the required queries elements for an OpenXR application
      on Android, so that runtime and layer components loaded in the application
      process may access their own package in API >29.
      (internal MR 2708)
    • New multi-vendor extension specification: XR_EXT_hand_interaction
      (internal MR 2116)
    • New multi-vendor extension specification: XR_EXT_plane_detection
      (internal MR 2510,
      internal MR 2781,
      internal MR 2791)
    • New multi-vendor extension specification: XR_EXT_hand_tracking_data_source
      (internal MR 2568)
    • New vendor extension specification: XR_META_passthrough_color_lut
      (internal MR 2507)
    • New vendor extension specification: XR_META_virtual_keyboard
      (internal MR 2555)
    • New vendor extension specification: XR_OPPO_controller_interaction
      (OpenXR-Docs PR 146)
    • Refine the spec language for a few MSFT extensions, including a clarification
      for controller model's dependency to an active grip pose action, and a
      correction to the xrTryCreateSpatialGraphStaticNodeBindingMSFT function's
      behavior.
      (internal MR 2600)
    • Remove incorrect/unused exception in the structure type value format rule.
      (internal MR 2762)
    • XR_EXT_debug_utils: Remove erroneous member documentation.
      (internal MR 2763,
      OpenXR-Docs issue 151,
      internal issue 2015)
    • XR_EXT_debug_utils: Clarify requirement on ending label regions.
      (internal MR 2763,
      OpenXR-Docs issue 150,
      internal issue 2014)
    • XR_FB_scene: Introduce XrSemanticLabelsSupportInfoFB and bump spec version to
      3.
      (internal MR 2682)
    • XR_FB_scene: Fixed specification language for XrRoomLayoutFB and
      XrBoundary2DFB which incorrectly described the input capacity parameter as
      referring to the number of bytes when, in fact, it refers to the number of
      elements in the array.
      (internal MR 2713)
    • XR_FB_scene: Clarified the meaning of the 2D and 3D bounding boxes obtained
      by xrGetSpaceBoundingBox2DFB and xrGetSpaceBoundingBox3DFB.
      (internal MR 2714)
    • XR_FB_scene: Clarify the behavior of xrGetSpaceRoomLayoutFB during the
      first call of the two-call idiom when the user retrieves the required buffer
      length.
      (internal MR 2715)
    • XR_FB_scene ...
Read more