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
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
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
- Crash on mdb_page_alloc when opening a project that was running while the PC shut down
- macOS Player freeze when using RunInBackground and Command+Tabbing to and from the application
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.