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
- 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
Add comment