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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment