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
- "Objects are trying to be loaded during a domain backup." errors on entering Playmode
- Transform Node does not have outputs when it is created
- Changing the Default Icon does not change the executable's icon when re-building the project
- Texture is stored upside down when using Blit
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
Add comment