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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
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