Search Issue Tracker
Active
Votes
0
Found in
2.2.0
Issue ID
UUM-133611
Regression
No
XRSettings compilation error appears when VR Built-in module is disabled while XR Composition Layer is installed
Reproduction steps:
1. Create a new project from VR Template
2. Install XR Composition Layer via Package Manager (Window → Package Manager)
3. Disable VR Module (com.unity.modules.vr) (in the Package Manager switch to “Built-in“ tab to find the VR Module)
4. Observe the result in the Console window
Actual result: “The name 'XRSettings' does not exist in the current context“ compilation error appears in the Console window
Expected result: No errors in the Console window
Reproducible in: 2.2.0 (6000.4.0b1) 2.3.0 (6000.4.0b1 - 6000.4.0b6)
Could not test with:
- Editor: 6000.0.66f1, 6000.3.6f1, 6000.4.0a5, 6000.5.0a5 (unable to disable the VR Module due to dependencies from other XR packages, which cannot be removed as XR Composition Layers package requires them to be present in the project)
- Package: 2.1.0 and earlier (different error appears due to incompatibility between 6000.4 beta version and the package version)
Reproducible on: Windows 11
Not reproducible in: No other environments tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Add comment