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
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
- Double separation lines are present in a kebab dropdown menu
- [URP] CommandBuffer: built-in render texture type 3 not found while executing warning is thrown when Game view is open and OpenGL is used
- User gets "Sorry...that page seems to be missing" when click a help icon
- Horizontal Scrollbar appears in the Inspector Window when the Volume Component is added
- Build Profiles - Feature Request: Editor restart button would improve the user experience
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!