Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.2.0
Issue ID
ISXB-140
Regression
No
[Input System] Out-of-focus DirectInput Gamepad devices do not set ButtonControl.wasPressedThisFrame correctly
Reproduction steps:
1. Connect a DirectInput Gamepad to your system
2. Download and open the attached project: "InputSystemBug.zip"
3. Open the SampleScene
4. Build and Run the Windows Standalone Player
5. In the Windows app, press buttonSouth on the Gamepad (Button A/ Cross)
6. Observe the number of presses being counted in the Game view
7. Click outside the Windows app to make it lose focus
8. Press buttonSouth again
Expected result: The number of presses in Game view is still being counted
Actual result: The number of presses stops being counted until the Game view is in focus again
Reproducible with: Input System 1.1.1, Input System 1.2.0, Input System 1.3.0 (2019.4.32f1, 2020.3.23f1, 2021.1.28f1, 2021.2.3f1, 2022.1.0a14)
Notes:
- Not reproducible in the Editor (2021.3+)
- Does not repro with Xbox controller
- Tested with a PS DualShock 4 V2 controller
- Attached project sets Application.runInBackground = true
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
There are no fixes planned for this Bug