Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2019.1.X
Votes
0
Found in
2019.1.0a10
2019.2.0a3
Issue ID
1121685
Regression
Yes
Line and Trail Renderers throw errors in the console when Inspector window is of certain dimensions
Steps to reproduce:
1. Download the attached project and open SampleScene
2. Make sure that you Inspector window is docked to the right of the Scene view, if it isn't already
3. In the Hierarchy panel, toggle between selecting Line and Trail Renderer game objects
4. Observe the errors in the console
Notes:
- Tested in Unity 2019.1.0a10, 2019.1.0b2, 2019.2.0a3
- Only reproduced with 2019.1.0a10 and above where the Inspector was converted to UIElements
- Only reproduces with Line and Trail renderers
- Reproduces across all render pipelines
- Does not reproduce with the default editor layout
- Here's the error message:
Layout update is struggling to process current layout (consider simplifying to avoid recursive layout): VisualElement unity-panel-container3 (x:0.00, y:0.00, width:557.00, height:790.00) world rect: (x:0.00, y:0.00, width:557.00, height:790.00)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment