XR_EXT_spatial_anchor creates entities in a standardized pose and context. Understand life cycle, discovery and what the extension does not guarantee.
Direct answer
The XR_EXT_spatial_anchor ratified extension of OpenXR 1.1.63 standardizes the creation of an anchor entity from base space, time, and pose within a configured spatial context. The anchor can be queried in snapshots and discovered in the parent context. Its basic life cycle ends with the context or the destruction of the entity; Cross-session persistence and cross-process sharing depend on other extensions and should not be assumed.
Common contract reduces adaptations per supplier
BaseSpace, time, and pose form a consistent input. The application can separate spatial logic from the specific code of each runtime.
Capacity needs to be negotiated
The context must include XR_SPATIAL_CAPABILITY_ANCHOR_EXT. Without enumeration and configuration, the call fails; portability requires conditional paths.
Identity is local to context
The ID allows you to query the entity in that context, but should not be treated as a global identifier. Other contexts may represent the same anchor with different IDs.
Anchor does not mean automatic persistence
The basic extension maintains the entity for the duration of the context. Saving between sessions or sharing requires additional features and permission policies.
Nexus Reading
Standardization improves architecture, but the product still needs to declare minimum support, fallback, desired persistence, and relocation tests at each target runtime.
FAQ
Is the extension ratified?
Yes. The registry page indicates XR_EXT_spatial_anchor revision 1 as ratified in OpenXR 1.1.63.
Does the anchor survive the end of the session?
Not guaranteed by this basic extension; persistence depends on additional extensions.
Does every OpenXR runtime offer the feature?
Not necessarily. The application must enumerate, enable, and configure the capability before use.
Essential guides to delve deeper into the decision
This editorial analysis was produced by Nexus from the official sources below, consulted on September 22, 2026. The text is original and interprets practical implications for companies.
- Khronos — XR_EXT_spatial_anchor: ratified status, revision, dependency, and extension surface.
- Khronos — xrCreateSpatialAnchorEXT: creation, capacity configuration, identification, discovery, and anchor lifecycle.
Date reported by main source: OpenXR 1.1.63 consulted on September 22, 2026; technical analysis.