Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0a1
2018.3.0a1
2018.3.7f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1145063
Regression
No
[UI] [legacy text] When text font used has references to the bold font - some fonts still use algorithmic bolding
Steps to reproduce:
1. Open QA attached project
2. Open "SampleScene"
3. Observe the NotoSansCJKtc-Regular.otf fond is too bold with "bold" font style
4. Import the NotoSansCJKTc-Bold.otf font and reimport NotoSansCJKtc-Regular.otf
5. Notice that there's no difference, especially looking at the "Canvas Low Res" text - algorithmic bolding is still used
Expected result: Algorithmic bolding should not be used if the font used has references to bold font
Reproduced in: 2019.3.0a1, 2018.3.7f1, 2017.4.26f1
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
- Previous model to world matrix is not correctly set for ASW
- More calls are made to GC.Alloc in an HDRP Sample Template when compared to the 2022.3 stream
- Generating Light Probe lighting returns inconsistent results on a specific mesh
- Two Warnings appear for every Soft Delete Operation when Deleting Sub Assets in the Project Browser
- “Item m_LightProbeSystem not found” warning is thrown when pressing the “Open” button multiple times in the Adaptive Probe Volume component warning
Resolution Note (2019.3.X):
Low priority defect and unlikely to be fixed for the near future.