Search Issue Tracker
Not Reproducible
Votes
0
Found in
5.5.3f1
Issue ID
941187
Regression
No
[Hololens] Spatial Mesh Collider does collide with a gaze pointer after tracking state lost
Steps to reproduce:
1. Open the attached project
2. Open the main.unity scene
3. Switch platform to Windows Store
4. Build for WSA Universal 10 SDK
5. Open Visual Studio solution
6. Deploy on Remote Machine (Hololens)
7. Loose tracking state by occupying the sensors for a few times
8. Observe, the gaze pointer will at some point not collide with some parts of spatial mesh since their colliders are inactive
Actual results: Spatial Mesh Collider does collide with a gaze pointer after tracking state lost
Expected results: Spatial Mesh Collider should collide normally
Note:
With 2018.1.0b1 I get "HLWM: Reading and writing a shared object on multiple threads simultaneously is not threadsafe!"
Reproduced with: 5.6.4p4, 2017.1.2.p4, 2017.2.1p2, 2017.3.0f3, 2018.1.0b1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment