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
- “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
Add comment