Search Issue Tracker
By Design
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
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.