Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2022.3.2f1
2023.1.1f1
2023.2.0a20
Issue ID
UUM-90318
Regression
No
Tracking does not recover on HoloLens 2 when moving to another space
How to reproduce:
1. On HoloLens 2 "Remove All Holograms" to clear the tracking data
2. Open the attached project "My project.zip"
3. Build And Run the project on HoloLens 2
4. Observe that spatial meshes are visible
5. Cover HoloLens 2 sensors
6. Go to another room
7. Uncover HoloLens 2 sensors
Expected results: Spatial meshes are visible
Actual results: Spatial meshes are not visible
Reproducible with: 1.7.0 (2022.3.2f1, 2023.1.1f1, 2023.2.0a20), 1.8.2 (2022.3.9f1, 2023.1.13f1, 2023.2.0b9, 2023.3.0a5)
Could not test with: 2021.3.30f1 (spatial meshes are not visible from the start)
Reproducible on: HoloLens 2
Not reproducible on: No other environment tested
Notes: The issue is resolved by using "{{xrInputSubsystem.TrySetTrackingOriginMode(TrackingOriginModeFlags.Unbounded);}}"
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2023.2.X):
There are no fixes planned for this Bug