Search Issue Tracker
Won't Fix
Votes
5
Found in [Package]
Input System preview.2 - 1.0.0
Issue ID
1192124
Regression
No
[XR][Input System] Binding Listen functionality does not work for XR controller inputs
How to reproduce:
1. Open the attached "VR-Input.zip" project
2. In the Project view, select "Input.inputactions" and click "Edit asset" in the Inspector
3. Select "<No Binding>" and open the "Path" dropdown
4. Select "Listen" and try pressing any button on any XR Controller
Expected results: The XR input is detected and shown in the "Path" dropdown
Actual results: The XR input is not detected
Reproducible with: 2019.2.13f1, 2020.1.0a13 (Input System preview.2 - 1.0.0)
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
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
- "Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
- MacOS persistentDataPath uses old path when built compared to Editor Play mode
- Crash on RaiseException when entering Play Mode in a specific project
- Debug Console does not reappear when disabling and re-enabling Debug.developerConsoleEnabled
Resolution Note:
This is because the XR Input system is not started until play mode is started. We are looking into enabling XR Input in the editor, but until then the work around is to enter play mode and then use the "listen" option of the new input system. This will then correctly detect the input from your XR Device