You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Valid Usage (Implicit) of XrCompositionLayerCubeKHR it says "Both of space and swapchainmust have been created, allocated, or retrieved from the same XrSession"
But for the other types of composition layers, this validity requirement is missing.
This seems like an oversight.
This is presumably because the handles in the other layers are not contained in the layer struct directly, but in a different (nested) struct.
E.g. XrCompositionLayerProjection contains pointers to potentially multiple XrCompositionLayerProjectionViews which contain a XrSwapchainSubImage which contains a swapchain.
I haven't checked if there are structs other than the composition layers that are affected by this.
The validity requirement is generated here but it only seems to check handles that are directly in the struct.
The text was updated successfully, but these errors were encountered:
An issue (number 2335) has been filed to correspond to this issue in the internal Khronos GitLab (Khronos members only: KHR:openxr/openxr#2335 ), to facilitate working group processes.
This GitHub issue will continue to be the main site of discussion.
In the Valid Usage (Implicit) of
XrCompositionLayerCubeKHR
it says "Both ofspace
andswapchain
must have been created, allocated, or retrieved from the same XrSession"But for the other types of composition layers, this validity requirement is missing.
This seems like an oversight.
This is presumably because the handles in the other layers are not contained in the layer struct directly, but in a different (nested) struct.
E.g.
XrCompositionLayerProjection
contains pointers to potentially multipleXrCompositionLayerProjectionView
s which contain aXrSwapchainSubImage
which contains aswapchain
.I haven't checked if there are structs other than the composition layers that are affected by this.
The validity requirement is generated here but it only seems to check handles that are directly in the struct.
The text was updated successfully, but these errors were encountered: