Search Issue Tracker
By Design
By Design in 2021.3.X
Votes
0
Found in
2021.3.20f1
Issue ID
UUM-29467
Regression
No
[2021.3] UI elements lose their position when entering Play Mode, and the “Reverse Arrangement” setting is enabled in the Vertical or Horizontal Layout Group component
How to reproduce:
1. Open the user’s attached “first-steps.zip” project
2. Open the “5_ComplexHierarchies” Scene (Assets > Scenes > 5_ComplexHierarchies)
3. Enter Play Mode and observe the UI in the bottom left corner
Expected result: UI doesn’t overlap
Actual result: UI overlaps
Reproducible with: 2021.3.20f1
Not reproducible with: 2022.2.0b8, 2022.2.10f1, 2023.1.0b7, 2023.2.0a5
Could not test with: 2020.3.46f1, 2022.1.0a1, 2022.2.0b7 (Errors after project downgrade)
Reproduced on: macOS 13.2.1 (Intel)
Notes:
Reproducible in the Editor and in the Standalone Player (macOS)
Not reproducible after disabling and enabling the “Reverse Arrangement” setting in the Vertical Layout Group component
Also reproducible with the Horizontal Layout Group component
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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Resolution Note:
The game objects that are children of the game object with a Vertical/Horizontal Layout Group have Content Size Fitters in them, which is what's causing the layout issue. The Content Size Fitters have a warning on them mentioning that the parent has a layout group component and therefore it shouldn't be used here as layout should be driven by the layout group. Working as designed.
Resolution Note (2021.3.X):
The game objects that are children of the game object with a Vertical/Horizontal Layout Group have Content Size Fitters in them, which is what's causing the layout issue. The Content Size Fitters have a warning on them mentioning that the parent has a layout group component and therefore it shouldn't be used here as layout should be driven by the layout group. Working as designed.