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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
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!