Search Issue Tracker
Fixed
Fixed in 2.5.0
Votes
0
Found in [Package]
2.4.0
2.4.1
Issue ID
XRIT-82
Regression
No
The Scene is bound to the Camera in HoloLens 2 when "Use XR Device Simulator in scenes" is enabled
How to reproduce:
1. Open the attached project "arfoundation-samples.zip"
2. Open Edit>Project Settings...
3. Select XR Plug-in Management>XR Interaction Toolkit
4. Enable "Use XR Device Simulator in scenes"
5. Build And Run the project on HoloLens 2
Expected results: The Scene is not bound to the Camera
Actual results: The Scene is bound to the Camera
Reproducible with: 2.4.0, 2.4.1 (2021.3.29f1, 2022.3.6f1, 2023.1.5f1, 2023.2.0a23)
Reproducible on: Windows 10
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
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
Resolution Note (fix version 2.5.0):
In XR 2.5.0, we have changed the automatic creation of the XR Device Simulator prefab to be excluded from standalone builds by default. A new **Instantiate In Editor Only** setting to control this behavior was added to the XR Interaction Toolkit project settings.