Search Issue Tracker
Fixed in 2019.2.X
Votes
0
Found in
2019.2.0a7
Issue ID
1132198
Regression
Yes
[Editor] Unable to change editor "Layout" after importing any asset or any package into the project
Layouts cannot be changed if any asset or any package is imported in the project, with the error on console "Menu Window/Layouts couldn't be found" on selecting "Layout"
Steps to Reproduce:
1. Create a new project.
2. Window > Package Manager > ProBuilder (Or any package) > Install
OR
2. Import any asset from Asset Store
OR
2. Import any .unitypackage file
3. Select "Layout" dropdown from the upper right corner of the editor.
Actual Result:
"Layout" dropdown doesn't open, with error "Menu Window/Layouts couldn't be found"
Expected result:
"Layout" dropdown opens up.
Reproducible on:
2019.2.0a7 (d06a032e8889)
Works on:
2019.2.0a6, 2019.1.0b5
Environment:
Both Windows and Mac
Error:
Menu Window/Layouts couldn't be found
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
- Crash on PrepareDrawShadowsCommandStep1 when entering the Play Mode in a specific project
- Physics Layer Collision Matrix's Layer names, checkboxes and hover highlights become misaligned when the Editor's UI Scaling gets changed
- Light/shadow information on an edge of a Terrain tile creates a seam with an adjacent Terrain tile when baking a LightMap
- "Missing types referenced from component UniversalRenderPipelineGlobalSettings on game object UniversalRenderPipelineGlobalSettings..." warning is thrown after switching the Platform to tvOS
- “Metal: Error creating pipeline state (Universal Render Pipeline/2D/Sprite-Lit-Default): Vertex attribute BLENDINDICES0(5) of type uint4 cannot be read using MTLAttributeFormatFloat2 (null)“ when setting GPU Skinning to GPU after opening the project
Alex_StudioDrydock
Oct 23, 2019 05:36
This is also happening in 2019.2.6f1 and 2019.2.9f1 for our project, but I have not figured out how to reproduce from a new project (adding the same set of packages did not repro the issue).