Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.45f1
2022.3.52f1
6000.0.25f1
6000.1.0a2
6000.2.0a1
6000.3.0a5
6000.4.0a1
6000.5.0a1
Issue ID
UUM-86396
Regression
No
Elements in UI Builder Viewport are displayed incorrectly when Editor UI Scaling is set to 125%
Reproduction steps:
1. Open the attached “IN-87332.zip” project
2. Make sure UI Scaling is set to ‘125%’ (Edit > Preferences > UI Scaling)
3. Open the “PlayerCardScene” Scene (Assets > Scenes)
4. Open the “TeamSheet.uxml” in the UI Builder (Assets > UI Toolkit > Documents > CompletedDocuments)
5. Select the “TeamSheet.uxml” in the UI Builder Hierarchy
6. Make sure Canvas Size is set to 1920 x 1080 or ‘Match Game View’ is enabled
7. Observe the difference between Game view and UI Builder Viewport
Expected result: Both views show the same
Actual result: In the UI Builder, only 3 player cards are shown instead of 4
Reproducible with: 2021.3.45f1, 2022.3.52f1, 6000.0.25f1, 6000.1.0a2
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Note:
- Could not reproduce with any other scaling percentage
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
- 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
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
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. The priority level is determined by factors such as the severity and frequency of an issue and the number of users affected by it. 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.