Search Issue Tracker
Fixed
Fixed in 2.1.1
Votes
0
Found in [Package]
2.1.0
Issue ID
XRCLB-143
Regression
No
[XR] XR Composition Layers are invisible when the MetaXR feature group is enabled
Steps to reproduce:
1. Open the attached user's project "XRCompositionLayersWithMetaXRSDK.zip"
2. Switch to Android
3. In OpenXR settings make sure MetaXR feature group is enabled
4. Build to a Quest 3/3S and observe Canvas not being rendered in Passthrough
5. Disable MetaXR Feature group and repeat step 4
Expected result: XR Composition Layers are visible when the MetaXR feature group is enabled
Actual result: XR Composition Layers are invisible when the MetaXR feature group is enabled
Reproducible with: XR Composition Layer 2.0.0 - 2.1.0 (2022.3.65f1, 6000.0.56f1, 6000.2.0f1, 6000.3.0a5)
Could not test below XR Composition Layer 2.0.0 due to editor getting stuck at "Requesting" for the specified version, manual Manifest.json editing also exhibits the same issue
Reproducible with these devices:
VLNQA00644 - Oculus Quest 3S (Quest 3S), CPU: Google Tensor G2, GPU: Adreno 740, OS: 14
VLNQA00609 - Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno 740, OS: 12
Environment tested: Windows 11 24H2
Notes:
-Issue only reproduces when Meta XR Feature Group is enabled
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2.1.1):
META BUG
https://unity3d.atlassian.net/browse/METUP-526