Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.2.0p1
Issue ID
970761
Regression
No
[Mixed Reality] Motion Controller positions are wrong when InputTracking.disablePositionalTracking is true
Steps to reproduce:
1. Open the attached project (OC)
2. Open the Main.unity scene
3. Play the scene (make sure that Mixed reality device and motion controllers are connected)
4. Watch the motion controller not being in front of you but somewhere else in space
Actual results: Then InputTracking.disablePositionalTracking is set to true, head tracking is not disabled
Expected results: Then InputTracking.disablePositionalTracking is set to true, head tracking should be disabled
Note:
MotionControllerVisualizer.cs:InputTracking.disablePositionalTracking on line 73
Reproduced with: 2017.2.1p2, 2017.3.0p3, 2018.1.0b4, 2018.2.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment