Search Issue Tracker
Fixed in 1.1.1
Fixed in 1.3.0
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
- 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 (fix version 1.1.1):
Fixed in: 2022.1.0a10 (1.1.1)
Resolution Note (fix version 1.3.0):
Fixed in: 1.3.0 (2021.2.11f1)
Resolution Note (fix version 1.1.1):
Fixed in: Input System 1.1.1 (2019.4.40f1)
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)