Search Issue Tracker
Fixed in 2020.2.17f1
Votes
1
Found in
2019.2
2019.2.8f1
2020.1
Issue ID
1189817
Regression
No
[XR][OpenVR][WMR] HMD's trackingState does not change when the device loses positional tracking
How to reproduce:
1. Open the attached "TrackingStateBug.zip" project
2. Enter Play mode
3. Inspect the Console and notice the device's tracking states are: Position, Rotation, Velocity, AngularVelocity
4. Cover up the cameras on the WMR device so it loses the positional tracking
5. Inspect the Console
Expected results: The device's tracking states are now: Rotation, Velocity, AngularVelocity
Actual results: The device's tracking states do not change
Reproduced in: 2019.2.13f1, 2020.1.0a13
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
- [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
Resolution Note (fix version 2020.2.17f1):
The XR Team cannot reproduce this issue on the lmost recent versions on Unity (2020.3+). For the best experience with XR input, we suggest using the new Input system: https://blog.unity.com/technology/introducing-the-new-input-system