Search Issue Tracker
Active
Under Consideration for 1.7.X, 1.8.X
Votes
0
Found in [Package]
1.7.0
1.8.2
Issue ID
OXRB-253
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);}}"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- ResolveUsePasses now extracts passes from all subshaders including fallbacks, in contrast to documented behaviour
- [UIBuilder] Changes aren't detected on types implementing IList
- [HDRP] Text is rendered with artefacts when using STP and resolution scale is set a float value
- [Settings Search] Search results not always matching search term correctly
- Crash on memcpy when opening a project that loads TSS files
Add comment