Search Issue Tracker
Fixed in 1.1.1
Votes
8
Found in [Package]
1.1.0-preview.2
Issue ID
1284586
Regression
No
[Input System] InputInteractionContext.timerHasExpired property breaks in Editor after waking up the PC from Sleep Mode
How to reproduce:
1. Open the attached "InputSleepIssue" project
2. Open Scenes/SampleScene
3. Put the PC to Sleep Mode
4. Wake up the PC
5. Enter Play Mode
6. Tap the left Mouse button
Expected result: "Fire started" and "Fire performed" messages are printed in the console window
Actual result: "Fire started" and "Fire canceled" messages are printed in the console window
Reproducible with: 1.0.0-preview(2019.4.13f1), 1.0.0(2020.1.9f1), 1.1.0-preview.1(2020.2.0b9), 1.1.0-preview.2(2021.1.0a2)
Can't test: 2018.4(Input System version is too old)
Notes:
- Might take several tries to reproduce the issue
- The user mentions that InputInteractionContext.timerHasExpired always returns true after waking up the PC, thus causing the bug
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
- Particle System isn't culled off-screen when the Culling Mode is set to Automatic and the Simulation Space is set to World
- [SceneView] Spline Knot placement ignores the visibility flags on gameobject
- 2px Softness is applied to RectMask2D when the Camera is set to Orthographic
- ShaderKeywordSet:GetEnabledKeywords crash
- FP32 is used for a temporary when compiling a shader for GLES or Vulkan
Resolution Note (fix version 1.1.1):
Fixed in: 2022.1.0a10 (1.1.1)
Resolution Note (fix version 1.1.1):
Fixed in: 1.1.1 (2021.1.28f1)
Resolution Note (fix version 1.1.1):
Fixed in: 1.1.1 (2020.3.22f1)