KhronosGroup / KhronosGroup/OpenXR-Docs

Clarification request: creating / modifying Guardian (Room-Scale) in OpenXR

Open
#190 3 comments 0 reactions 0 assignees View on GitHub
synced to gitlab
Dominant language
Python
Stars
181
Forks
74
PR merge metrics
No merged PRs in 30d

Description

Hi,

We are developing an enterprise app for **Meta Quest 3** using **Meta-OpenXR**.
Currently, switching from *Stationary* to *Room-Scale* can only be triggered through system UI or via `OVRBoundary.RequestBoundarySetup()` (Oculus XR Plugin), which is not available in OpenXR.

- The spec 1.1 (Stage reference space) states that the Stage is created “at the runtime’s discretion”.
- No published extension exposes Guardian setup.

Could you confirm that there is **no existing OpenXR API** (KHR/EXT) to
1) trigger the creation or re-definition of a Room-Scale Guardian, or
2) automatically extend the Play Area on first app launch?

Would the WG welcome a proposal for an extension (e.g. `XR_META_boundary_setup`) that exposes an `xrRequestBoundarySetup()` call similar to the OVR API?

Thank you for your insights.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the OpenXR 1.1 Stage reference space text and review the published KHR/EXT extensions against the requested Guardian operations. Compare the question with OVRBoundary.RequestBoundarySetup and the proposed XR_META_boundary_setup entry point. Done means an authoritative WG response addresses API availability, automatic Play Area extension, and whether an extension proposal is welcome.

Written by the indexing model from the issue text.

Assessment

Domain
api, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.