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.
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
- Symlinks are broken when a package which contains .xcframework + symlinks is added through Unity Package Manager.
- Crash on ApplyMaterialPass when opening a specific scene
- Memory leak when using Native Plugin in Windows IL2CPP Build
- [URP][Tutorial] Universal 3D Sample tutorial issues
- Gradle error: "...Unexpected error during link..." is thrown when building for Android and targeting API Level 34
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.