Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0f3
Issue ID
984157
Regression
No
GestureRecognizer with all three GestureSettings.Navigation flags does call NavigationUpdated
Steps to reproduce:
1. Open the attached project
2. Open the TestScene.unity scene
3. Play the scene (make sure that Mixed reality device and motion controllers are connected)
4. Hold the grip button and move the MotionController in front of the HMD
5. Note the Debug.Log always stays the same
Actual results: Using the GestureRecognizer with all three GestureSettings.Navigation flags does call NavigationUpdated, but the returned TryGetPosition/-Rotation values are always the same value the controller started with
Expected results: Using the GestureRecognizer with all three GestureSettings.Navigation flags should call NavigationUpdated and the return the updated values
Note:
Unable to test with 2018.1.0b4 due another issue
Reproduced with: 2017.2.1p2, 2017.3.0p3, 2018.2.0a1
Add comment
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
Resolution Note (2019.1.X):
XR Management has evaluated this issue and determined that it does not meet our current bug severity threshold. If you would like your issue to be reviewed again, please re-submit your bug.