Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2017.4.6f1
2018.2.0a1
Issue ID
1061283
Regression
Yes
Incorrect Layout when using Nested ContentSizeFitters and LayoutGroups with ForceRebuildLayoutImmediate
Steps to reproduce:
1. Open QA-supplied project
2. Open Scene "test"
3. Enter Play Mode
Expected: Content gets distributed within the bounds
Actual: Content exits the bounds
Reproduced in: 2018.2.0a1, 2018.2.0f2, 2018.3.0a5
Not reproduced in: 2017.1.4p2, 2017.2.3p2, 2017.3.2f1, 2017.4.7f1, 2018.1.9f1
Note: the screenshot with the content in the top right corner is prior to 2018.2 and the content that is out of bounds is post-2018.2
Hard to say if this is a bug since prior to 2018.2 there was an issue as well because the content was in the top right corner and ignored ForceRebuildLayoutImmediate at the Start of the scene, but the content was put in order when the user pressed Ctrl+R
Post-2018.2 the layout stays the same, ignoring the bounds, even if you press Ctrl+R
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment