Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X, 2023.1.X
Votes
0
Found in
2021.3.8f1
2022.1.12f1
2022.2.0b5
2023.1.0a6
2023.2.0a1
Issue ID
UUM-13135
Regression
Yes
UI Elements are not wrapping correctly at certain Aspect Ratios when changing the Aspect Ratio of the Game Tab
How to reproduce:
1. Open the user-attached project “TestProject-Wrap”
2. Set Game Tab to use Free Aspect Ratio
3. Change the size of the Tab
4. Observe the Game View
Expected result: UI Elements are wrapped only when the Game Tab is narrow
Actual result: UI Elements are wrapped at random Aspect Ratios
Reproduced with: 2021.2.2f1, 2021.3.8f1, 2022.1.0a13, 2022.1.12f1, 2022.2.0b5, 2023.1.0a6
Not reproduced with: 2021.2.1f1, 2022.1.0a12
Couldn’t test with: 2020.3.37f1 (Scripts can’t be loaded, UI is not rendered)
Reproduced on: Windows 11 Pro
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note:
Thank you for bringing this issue to our attention. After careful consideration, we have determined that other higher-priority issues should take precedence, and we have decided not to address your issue at this time. We have future work planned that will improve the situation. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.
Resolution Note (2023.1.X):
Thank you for bringing this issue to our attention. After careful consideration, we have determined that other higher-priority issues should take precedence, and we have decided not to address your issue at this time. We have future work planned that will improve the situation. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.
Resolution Note (2022.2.X):
This will be addressed with future rework of the layout caching