Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2020.1.X
Votes
0
Found in
2020.1.0a22
Issue ID
1216574
Regression
Yes
[IMGUI] Assertion failed errors when docking an editor window containing a GUILayout.window
1. Create a new project.
2. Install ProBuilder through the package manager.
3. Open the ProBuilder window. (Tools -> ProBuilder -> ProBuilder Window)
4. Open the UV Editor window. (ProBuilder Window -> UV Editor)
5. Dock the UV Editor window anywhere.
Expected Outcome: No issues, no errors.
Actual Outcome: Continuous errors in the console.
Reproducible in 2020.1.0a22 with ProBuilder preview.2 4.3.0, 4.1.0. Doesn't seem to be package specific.
Not reproducible in 2020.1.0a21 with ProBuilder preview.2 4.3.0
Error Message:
Assertion failed on expression: '!dest.m_MultiFrameGUIState.m_Windows'
Notes:
- Tested on Windows and Mac.
- Errors can be cleared, but will continue to print to console until you restart the project.
- GIF attached demonstrating the issue.
- Tried other Probuilder windows, no apparent issues.
- Tried other dockable editor windows, no apparent issues. Unsure if there are any other windows affected by this.
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
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
- White lighting artifact when a point light with a small emission range and "Hard Shadows" touches an object while a directional light with "Soft Shadows" and another point light are present
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a1
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b1