Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.65f1
6000.3.3f1
6000.4.0b3
6000.5.0a4
Issue ID
UUM-132219
Regression
Yes
Font character thickness does not adjust properly in UI Toolkit text when changing Bold Weight in Font Asset
How to reproduce:
1. Open the attached "IN-129614_Test Font Asset.zip" project
2. In the Project window, double-click on "Test" to open it in UI Builder
3. In UI Builder, select the "Bold_Default" label element
4. In UI Builder’s inspector, navigate to "Text" and double-click on the assigned font asset
5. In the Inspector, change the selected font's Bold Weight (under Font Weights) to 3
6. Observe the label element in the UI Builder
Actual result: Font characters become wider, character thickness does not evenly increase in all directions
Expected result: Font character thickness increases evenly in all directions
Reproducible with: 2023.1.0a22, 6000.0.65f1, 6000.3.3f1, 6000.4.0b3, 6000.5.0a4
Not reproducible with: 2023.1.0a21
Reproducible on: Windows 11
Not reproducible on: No other environments tested
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. We changed the approach in TextCore to stay away from a Material approach, which enabled multi-threading for us. This feature was not ported correctly, and fixing it at this this involves a lot of risk and work. However, in 6.3+, you can start using ATG (Advanced Text), which fully supports this feature, and more!
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. We changed the approach in TextCore to stay away from a Material approach, which enabled multi-threading for us. This feature was not ported correctly, and fixing it at this this involves a lot of risk and work. However, in 6.3+, you can start using ATG (Advanced Text), which fully supports this feature, and more!