Ratified extent describes floor, wall, table, and 2D meshes by spatial components. See portability, trust, and physical QA.
Direct answer
The XR_EXT_spatial_plane_tracking extension of OpenXR 1.1.63 defines a portable capability for discovering spatial planes and querying components such as alignment, semantic label, 2D polygon, and 2D mesh. The standard allows an application to represent a floor, ceiling, wall or table without initially relying on a proprietary API. However, support, density, classification, and stability vary by runtime and environment. Enterprise experiences must enumerate capabilities, address missing or changing tracking, and validate physical tolerances before using a plan for positioning, security, or measurement.
Plan becomes consultable entity
The application discovers entities in a snapshot and requests only the necessary components, reducing coupling with a specific supplier.
Semantics is hypothesis, not truth
A runtime can label a surface as a table or wall, but confidence and availability vary. Experience must allow correction or fallback.
Polygon defines better than rectangle
True contours help avoid off-surface positioning, although cutouts, objects, and changes to the environment still require updating.
Tracking can degrade
Light, texture, occlusion, and movement affect stability. The product must report loss of tracking and avoid dangerous actions with uncertain pose.
Nexus Reading
Use the pattern for portability, but establish physical criteria per case: accuracy, latency, minimum area, tolerance, and safe behavior when the plan disappears.
FAQ
Is the extension ratified?
Yes. The OpenXR 1.1.63 Khronos registry marks XR_EXT_spatial_plane_tracking as ratified.
Does it identify surface types?
The extension includes alignment components and semantic labels when offered by the runtime.
Can it be used as a certified measuring instrument?
API standardization does not certify metrological accuracy; any use of measurement needs specific validation.
Essential guides to delve deeper into the decision
This editorial analysis was produced by Nexus from the official sources below, consulted on September 30, 2026. The text is original and interprets practical implications for companies.
- Khronos — XR_EXT_spatial_plane_tracking: ratified status, dependency and plan components, alignment, semantics and geometry.
- Khronos — XR_EXT_spatial_entity: common spatial model context, capabilities, snapshots, queries, and states.
Date reported by main source: OpenXR 1.1.63 consulted on September 30, 2026; ratified standard analysis.