InputInteractionContext.timerHasExpired property breaks in Editor after PC left Sleep Mode

Unity Engine
,
1

Usually, we didn’t power-off our PC’s while developing. And we faced funny bug with Input system (1.0.0, 1.1.0 and couple of versions below 1.0.0, but don’t remember how long we see this bug).
Bug itself - we’re working in Unity as usually (bug reproducible on 2020.1+ (currently we using 2020.1.7f1), maybe even before 2020, don’t remember) then send PC to Sleep Mode. Then wake up PC (just immediately after going to Sleep Mode or later, doesn’t matter) and all actions which relate to Tap interaction stop working properly. An InputActionPhase.Performed event never fires, only InputActionPhase.Starded and InputActionPhase.Canceled

6410118--715872--upload_2020-10-12_20-6-8.png
6410118--715872--upload_2020-10-12_20-6-8.png983×411 38 KB

InputInteractionContext.timerHasExpired always return true (m_Flags always 0) after setting m_TapStartTime (changing Tap duration to longer values didn’t affect in this case anything, like global timer itself stuck on some old value before sleep mode and it breaks m_Flags bitmask calculation)

6410118--715878--upload_2020-10-12_20-14-22.png
6410118--715878--upload_2020-10-12_20-14-22.png796×333 13.7 KB

6410118--715875--upload_2020-10-12_20-10-54.png

And it will start work again, without any changes in code\assets, only after restarting editor, but it’s really annoying :slight_smile:

2

Think this needs addressing as part of the focus handling overhaul. PC sleep should be treated equivalent to focus loss. Which implicitly should take of resetting the actions properly.

Would you mind filing a ticket with the Unity bug report (“Help >> Report a Bug…” in the Unity editor’s main menu) for this? Would help making sure we’re tracking this properly.

3

Yep, sure. A description like in this thread will be enough? (also will put link to this thread)

4

Case 1284586

1 Like