Search Issue Tracker
Duplicate
Votes
2
Found in
2017.3.0f3
Issue ID
985848
Regression
No
XRNodeState.TryGetAngularVelocity returns incorrect values while using OpenVR SDK
Steps to reproduce:
1. Download the latest attached project(XRNODEBUG.zip)
2. Open the project
3. Enable VR and set SDK to OpenVR
4. Enter playmode
5. Rotate Oculus controllers
6. Observe the reported values
Expected result: between 0 and a high value
Actual result: reported values between 0 and 1
Reproduced on 2017.2.0b1, 2017.2.1p1, 2017.3.0p3, 2018.1.0b4
XRNodeState unavailable on lower versions
While on Oculus SDK, the angular velocity is reported normally
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
- 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
Daniel-Ernst
Feb 07, 2018 09:53
Got the same issues in 2017.3.0f3 with openVR and my Vive. Only difference is that the angular velocity returns values between -1 and 1 in the angular velocity vector.
Hope this can be solved soon!