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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
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