C Specification

The XrSystemSpatialMeshPropertiesBD structure is defined as:

// Provided by XR_BD_spatial_mesh
typedef struct XrSystemSpatialMeshPropertiesBD {
    XrStructureType    type;
    void*              next;
    XrBool32           supportsSpatialMesh;
} XrSystemSpatialMeshPropertiesBD;

Members

Member Descriptions
  • type is the XrStructureType of this structure.

  • next is NULL or a pointer to the next structure in a structure chain.

  • supportsSpatialMesh is an XrBool32, indicating if current system is capable of spatial mesh functionality.

Description

An application can inspect whether the system is capable of spatial mesh functionality by chaining an XrSystemSpatialMeshPropertiesBD structure to the XrSystemProperties::next chain when calling xrGetSystemProperties.

If a runtime returns XR_FALSE for supportsSpatialMesh, the system does not support spatial mesh functionality, and the runtime must return XR_ERROR_FEATURE_UNSUPPORTED from xrCreateSenseDataProviderBD when called with XR_SENSE_DATA_PROVIDER_TYPE_MESH_BD. The application should avoid using spatial mesh functionality when supportsSpatialMesh is XR_FALSE.

If XrSystemSpatialSensingPropertiesBD::supportsSpatialSensing is XR_FALSE, then supportsSpatialMesh must also be XR_FALSE.

If a runtime returns XR_TRUE for supportsSpatialMesh, the system supports spatial mesh functionality. This implies that XrSystemSpatialSensingPropertiesBD::supportsSpatialSensing must also be XR_TRUE.

Note that supportsSpatialMesh may be XR_TRUE even if running on an Android-based platform and the application does not have the required com.picovr.permission.SPATIAL_DATA permission both declared in the manifest and granted at runtime. Evaluation of permissions takes place later, in the asynchronous operation started by xrStartSenseDataProviderAsyncBD.

Valid Usage (Implicit)

See Also

Document Notes

For more information, see the OpenXR Specification

This page is extracted from the OpenXR Specification. Fixes and changes should be made to the Specification, not directly.

Copyright 2014-2025 The Khronos Group Inc.