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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2018.3.X):
With the transition to XR Plugins, legacy implementations are being left as-is barring extenuating circumstances.