Search Issue Tracker
Fixed in 0.3.0-preview
Votes
0
Found in [Package]
0.0.9-preview
Issue ID
1093838
Regression
No
[XR] Usage {Primary2DAxisClick} didn't work
Migrated bug from GitHub: https://github.com/Unity-Technologies/InputSystem/issues/285
Usage {Primary2DAxisClick} referenced in https://docs.google.com/spreadsheets/d/1XqSzYRHGAbzW9uRi_8t2Xm_zfBEJHCS2Bp3dkAYsOQc/edit#gid=0 didn't work.
This has been tested on Oculus Rift and HTC Vive (don't know if it work on WMR).
Using Unity 2018.2.11.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
Add comment