Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0b3
Issue ID
1083169
Regression
Yes
Daydream Angular Acceleration is showing incorrect values
Steps to reproduce:
- Load the attached project
- Open the XRNodePhysicalTryGets scene
- deploy to Daydream
Expected:
The physical values for each node should be correct
Observed:
For whichever hand the remote is mapped to, acceleration, rotation, and angular acceleration show as available. The angular acceleration shows static, incorrect values.
I suspect angular acceleration should just show as not available?
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
Resolution Note (2018.3.X):
With the transition to XR Plugins, legacy implementations are being left as-is barring extenuating circumstances.