Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
3
Found in [Package]
1.1.0-pre.5
Issue ID
1334481
Regression
No
[Input System] .wasPressedThisFrame is false after Thread.Sleep() and InputSystem.Update()
Reproduction steps:
1. Open attached project "ThreadSleep.zip" and scene "SampleScene"
2. Enter Play Mode
3. Press keyboard keys rapidly and continuously
4. Observe Console window
Expected result: wasPressedThisFrame is true and logged
Actual result: wasPressedThisFrame is false and not logged
Reproducible with: 1.1.0-pre.5 (2019.4.29f1, 2020.3.13f1, 2021.1.13f1, 2021.2.0b1)
Comments (3)
-
oobartez
Dec 03, 2021 11:10
(v 1.1.1)
-
oobartez
Dec 03, 2021 11:08
This is affecting all our players.
-
kamil-dawidow
Sep 03, 2021 12:25
I'm still experiencing this problem. What's the ETA on a fix?
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:
Postponing until further notice due to higher priority needs. We hope to revisit this at a later time.