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
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Add comment