Search Issue Tracker
Fixed in 2019.1.X
Votes
6
Found in
2018.3.0f2
Issue ID
1110639
Regression
Yes
Tracked pose driver - Lost tracking bug
Steps to Reproduce:
- Set up an Oculus Rift
- Use Editor 2019.2.0a2
- Open the attached reproduction project "TPD Test.zip" with
- Open SampleScene.unity
- Press Play
- Hide a controller from the tracking cameras.
Expected Behavior:
When camera tracking is lost for a controller the position should remain at its last known good value.
Observed Behavior:
When camera tracking is lost for a controller the position returns to the scene origin. This is most easily observed through the scene view.
Tracked Pose Driver should be using TryGets for position and rotation. If position is not updated by the sdk, the last known good values should stick.
Note 2018.3 still uses TrackedPoseDriver in managed distributed C#, rather than TPD from the XR Legacy Helpers package.
Comments (4)
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
KospY
Jan 23, 2019 08:22
I saw that it has been fixed in Unity 2019.1, but it's an alpha, it's not really a solution.
Please fix it for 2018.3!