Search Issue Tracker
Duplicate
Votes
0
Found in
2017.2.0b5
2017.3.0f2
Issue ID
977791
Regression
Yes
Assertion failed error is thrown after pausing the game with a shortcut key and stepping one frame
Steps to reproduce:
1. Create a new project
2. Enter Playmode
3. Press Ctrl+Shift+P or Cmd+Shift+P at the same time
4. Press "Step" button
--Assertion failed error occurs
Error: "Assertion failed: Assertion failed on expression:
'!dest.m_MultiFrameGUIState.m_NamedKeyControlList'UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)"
Reproducible with: 2017.2.0b5, 2017.2.1f1, 2017.3.0f2, 2018.1.0a3
Not Reproducible with: 2017.1.2p4, 2017.2.0a4
Regression introduced in 2017.2.0a4
Is not reproducible with 2018.1.0a4, a5, a6, a7
Comments (4)
-
GrzegorzB83
Mar 25, 2018 17:47
SKIRNERS1
"I get this issue just from pausing and stepping in 2017.3"
me too. Can You fix it? -
dave_oak
Mar 15, 2018 14:42
Reproduced in 2017.3.1p4
More seriously, it occurs when building for Gameroom and aborts the build.
-
IgnisV
Mar 10, 2018 17:15
SKIRNERS1
"I get this issue just from pausing and stepping in 2017.3"
me too -
skirners1
Feb 18, 2018 14:50
I get this issue just from pausing and stepping in 2017.3
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
- Lightmap Asset icon changes colours after Baked Lightmap Viewer window is opened
- VideoClipImporter preset not applied when applying Preset Selector on already imported video clips
- Frame Debugger gets disabled when any Editor window is maximised and minimised
- TextMeshPro InputField view is not updated when OnEndEdit is triggered
- The "Open Frame Debugger" button in the Game View toolbar not only opens the Frame Debugger window but toggles between enabling/disabling the Frame Debugger when pressed
This is a duplicate of issue #949028