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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
Add comment