Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.4.X, 2018.1.X
Votes
0
Found in
2017.1.0f3
Issue ID
990728
Regression
No
[XR] No consistency between Unity's input tracking and WSA input information in Windows Mixed Reality
How to reproduce:
1. Download attached project file and open "testscene" Scene
2. Change Platform to UWP
3. Enter Play Mode
4. Move Mixed Reality controller
Actual result: When retrieving the node information for the right and left positional controllers, position and rotation are correctly displayed, but velocity and angular velocity aren't. The same information is correctly retrieved when using WSA API
Reproduced with: 2017.2.1p2, 2017.3.0p3, 2018.1.0b4
Note: Tested on Acer Windows Mixed Reality Headset
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
- Black square “shadow” artifacts visible when using Screen Space Reflections without maximum smoothing
Add comment