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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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.