[OpenXR] Adds a minimal API to request and control Passthrough #2141
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Details
Description
Follow up on #2119 and #2121. It adds the following new public APIs:
VRDeviceSystem.RequestPassthrough
- needs to be set in order for the OpenXR extension to get considered.VRRendererSettings.RequestPassthrough
- can be set in GameStudio and get passed to the VR device system by theForwardRenderer
VRDevice.SupportsPassthrough
- does the device support it?VRDevice.StartPassthrough
- needs to be called by user code to turn the feature onThe PR is a little bit different to the original one not exposing internal classes to the user. Not entirly sure here what is the best approach. It's only supported by OpenXR and there also by some devices, but having to cast on these types manually in Stride game code seems awkward as well.
Related Issue
#2119 and #2121
Types of changes
Checklist