Search Issue Tracker
By Design
By Design in 2023.3.X
Votes
0
Found in
2021.3.30f1
2022.3.9f1
2023.1.12f1
2023.2.0b8
2023.3.0a4
Issue ID
UUM-48219
Regression
No
Buttons do not correspond to the Vertical Layout Group settings when the scene loads for the first time
Reproduction steps:
1. Open the attached “ IN-51697 Vertical Layout Group Bug.zip“ project
2. Open the “SplashScreens” scene
3. Enter Play mode
4. Wait until the “MainMenu” scene loads
Expected result: The buttons on the right of the Game view spawn separated from each other
Actual result: The buttons on the right of the Game view spawn on top of each other
Reproducible with: 2021.3.30f1, 2022.3.9f1, 2023.1.12f1, 2023.2.0b8, 2023.3.0a4
Reproduced on: Windows 11 Pro (22H2)
Not reproduced on: No other environment tested
Notes:
- Could not reproduce in a new project
- In 2021.3.30f1, the button positions are in a different order
- Adjusting Vertical Layout Group settings in the Inspector or the Game view size resets the button spacing back to the way it was actually set
- Reproducible in Player
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note:
The game objects that are children of the game object with a Vertical 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 (2023.3.X):
The game objects that are children of the game object with a Vertical 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.