Goal Extension provides triangular mesh associated with spatial entities. See how to use it for occlusion, security and digital twins without losing portability.

Direct answer

The `XR_META_spatial_entity_mesh` extension allows you to obtain a triangular mesh linked to an OpenXR spatial entity. It depends on `XR_FB_spatial_entity`, uses OpenXR 1.0 and is not ratified by Khronos. Geometry can support occlusion, collision, positioning, and environmental understanding, but support varies by runtime. Applications need to query capabilities, limit map storage, and provide fallback when the mesh does not exist or is out of date.

Mesh transforms space into operational data

Triangles let you test depth, occlusion, and collision with captured surfaces.

Entity gives persistent reference

Linking geometry to a space helps you update and identify elements between supported operations.

Environment map is sensitive

Plant, machinery and circulation can reveal information; retention and access should be minimal.

Vendor extension requires fallback

The application must query support and downgrade to limits, plans, or manual configuration.

Nexus Reading

Use the mesh only where it improves the task, record version and confidence, and revalidate after physical changes.

FAQ

Is the extension part of the OpenXR core?

No. It is an extension of the Meta and is not ratified by Khronos.

What information does it provide?

A triangular mesh associated with a spatial entity.

How to preserve portability?

Detect support at runtime and implement an alternative path.

Essential guides to delve deeper into the decision

Primary sources and references

This editorial analysis was produced by Nexus from the official sources below, consulted on October 5, 2026. The text is original and interprets practical implications for companies.

Date reported by main source: OpenXR 1.1.63 specification verified October 5, 2026.