Search Issue Tracker
Fixed in 1.1-pre.5
Votes
1
Found in [Package]
1.0.0
Issue ID
1332850
Regression
No
[Input System] Out-of-focus Gamepad devices do not set ButtonControl.wasPressedThisFrame correctly
Reproduction steps:
1. Open the attached user's project "InputSystem Bug.zip"
2. Connect a xinput compatible controller
3. In the Project Window under the "Scenes" Folder open "SampleScene.unity"
4. Enter Play Mode
5. Hold Button A (South Button) on the controller
6. Observe that the debug message in the Console Window "TestControl was pressed this frame" only appears once
7. While still in Play Mode bring the Editor out of focus
8. Hold Button A (South Button) on the controller
9. Observe that the debug message in the Console Window "TestControl was pressed this frame" is continuously printed
Expected result: debug message in the Console Window "TestControl was pressed this frame" only appears once when the Editor is out of focus
Actual result: debug message in the Console Window "TestControl was pressed this frame" is continuously printed when the Editor is out of focus (See attached InputSystem.mp4)
Reproduces on: Input System 1.0.0, Input System 1.1.0 - preview.2 (2019.4.26f1, 2020.3.7f1, 2021.1.6f1, 2021.2.0a16)
Could not test: Input System 1.1.0 - preview.3 due to the input not being registered when the Editor is out of focus
Devices used for testing:
Xbox Series X wireless controller
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
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
Resolution Note (fix version 1.1-pre.5):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1324