Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 2017.1.X, 2017.2.X
Votes
4
Found in
2017.1.0f3
Issue ID
931840
Regression
Yes
[VR] Disabled positional tracking is ignored by camera's child transforms
When InputTracking.disablePositionalTracking is set, child transforms of the VR camera are still placed in the world as though positional tracking was being applied.
Reproduction Steps:
1. Run the updated projected (in comments, below)
2. Move the VR headset around, observe the child transform (cube) moving with the headset
3. Press RMB/Fire2 to disable positional tracking
4. Observe that the cube continues to be positionally tracked in the world where the camera "should be"
Expected Results:
When positional tracking is disabled for VR, all parts of the child hierarchy should also stop being tracked too.
Reproducible in version 2017.1.0p2.
Not reproducible in version 5.6.3f1.
Comments (2)
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
SoloChristian
Feb 24, 2018 00:32
This is still broken
EyePD
Oct 12, 2017 15:23
This applies to the camera GameObject as well. I started a new project with 2017.1.1f1, enabled VR and then attached a script to my camera object with a Start() function that calls UnityEngine.VR.InputTracking.disablePositionalTracking = true. When I run, the position of the camera object is clearly changing constantly in the Inspector as I move my Rift. I also tried making the call from Update but there was no difference.