Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2017.2.1f1
Issue ID
1001658
Regression
No
[Windows Mixed Reality] After "Lost boundary" camera sometimes gets zero vertical or much higher position
How to reproduce:
1. Download MixedRealityToolkit https://github.com/Microsoft/MixedRealityToolkit-Unity and open on Unity
2. Open /Assets/HoloToolkit-Examples/Prototyping/Scenes/Primitives.unity Scene
3. Switch platform to UWP and enter Play Mode
4. Force Mixed reality device to lost boundary(close sensors with hands until controller becomes irresponsible)
5. After controller response again, try to move with joystick
6. Repeat 4-5 steps
Actual result: Project with Microsoft Mixed Reality camera sometimes has zero vertical position when start player, Sometime camera position get to real height in few seconds, sometimes not till you recalibrate Headset.
Reproduced with: 2017.2.1f1, 2017.2.2f1, 2017.3.1p3, 2018.1.0b9
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment