C Specification

The xrStopColocationDiscoveryMETA function is defined as:

// Provided by XR_META_colocation_discovery
XrResult xrStopColocationDiscoveryMETA(
    XrSession                                   session,
    const XrColocationDiscoveryStopInfoMETA*    info,
    XrAsyncRequestIdFB*                         requestId);

Parameters

Parameter Descriptions

  • session is an XrSession in which the colocation discovery will be active.

  • info is a pointer to XrColocationDiscoveryStopInfoMETA structure to specify the stop discovery request information.

  • requestId is an output parameter, and the variable it points to will be populated with the ID of this asynchronous request.

Description

The application can call xrStopColocationDiscoveryMETA to stop an ongoing discovery process that was started by xrStartColocationDiscoveryMETA.

If the system does not support colocation advertisement and discovery, the runtime must return XR_ERROR_FEATURE_UNSUPPORTED from xrStopColocationDiscoveryMETA. In this case, the runtime must return XR_FALSE for XrSystemColocationDiscoveryPropertiesMETA::supportsColocationDiscovery when the function xrGetSystemProperties is called, so that the application knows to not use this functionality.

This is an asynchronous operation. Completion results are conveyed in the event XrEventDataStopColocationDiscoveryCompleteMETA.

If the asynchronous operation is scheduled successfully, the runtime must return XR_SUCCESS.

If and only if the runtime returns XR_SUCCESS, the runtime must queue a single XrEventDataStopColocationDiscoveryCompleteMETA event identified with a requestId matching the requestId value output by this function, referred to as the "corresponding completion event."

(This implies that if the runtime returns anything other than XR_SUCCESS, the runtime must not queue any XrEventDataStopColocationDiscoveryCompleteMETA events with requestId field matching the requestId populated by this function.)

If the asynchronous operation is successful, in the corresponding completion event, the runtime must set the XrEventDataStopColocationDiscoveryCompleteMETA::result field to XR_SUCCESS.

If the asynchronous operation is scheduled but not successful, in the corresponding completion event, the runtime must set the XrEventDataStopColocationDiscoveryCompleteMETA::result field to an appropriate error code instead of XR_SUCCESS.

Valid Usage (Implicit)
Return Codes
On success, this command returns

  • XR_SUCCESS

  • XR_SESSION_LOSS_PENDING

On failure, this command returns

  • XR_ERROR_FUNCTION_UNSUPPORTED

  • XR_ERROR_VALIDATION_FAILURE

  • XR_ERROR_RUNTIME_FAILURE

  • XR_ERROR_HANDLE_INVALID

  • XR_ERROR_INSTANCE_LOST

  • XR_ERROR_SESSION_LOST

  • XR_ERROR_RUNTIME_UNAVAILABLE

  • XR_ERROR_FEATURE_UNSUPPORTED

  • XR_ERROR_EXTENSION_NOT_PRESENT

See Also

XR_META_colocation_discovery, XrAsyncRequestIdFB, XrColocationDiscoveryStopInfoMETA, XrSession, xrStartColocationDiscoveryMETA

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

Copyright 2014-2025 The Khronos Group Inc.

This work is licensed under a Creative Commons Attribution 4.0 International License.