Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.4.2f2
Issue ID
873501
Regression
No
VR.InputTracking.disablePositionalTracking takes 1 frame, unlike other transform updates
How to reproduce:
1. Open user provided project
2. Build and run on device
3. Inspect debug output
Expected behaviour: Disabling positional tracking updates camera's transform in the same frame
Actual behaviour: Camera's position updates in the next frame
Reproduced with: 5.4.2f2-GVR11, 5.4.2f2-GVR12, 5.4.2f2-GVR13, 5.6.0b7*
- UnityEngine.VR.InputTracking.disablePositionalTracking is available from 5.6, but it was possible to use it in older versions by importing GVR plugin.
Reproduced with:
Google Pixel XL on Daydream
Samsung Galaxy S6 Edge on Oculus
HTC Vive on OpenVR
Comments (1)
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
mmsteve
Aug 08, 2017 08:58
This is not fixed 2017.1.0f3
Despite InputTracking.disablePositionalTracking returning true every frame, positional tracking is still enabled.