Search Issue Tracker
Won't Fix
Won't Fix in 6000.3.X
Votes
0
Found in
2022.3.66f1
6000.0.58f1
6000.2.5f1
6000.3.0b2
Issue ID
UUM-117589
Regression
No
Font Asset Creator Padding has no limit and shows incorrect Padding in results when Font Atlas is generated
Steps to reproduce:
- Create a new Unity project using the Universal 3D template
- Import the provided Font in the Attachments
- Open the Font Asset Creator window (Window > Text > Font Asset Creator)
- Select the imported Font as the Source Font
- Change Padding to a very large number ("538761590387518230957123" for example)
- Generate Font Atlas
- Observe the results in the Font Asset Creator window
Actual results: Padding has no limit and the results show incorrect Padding number
Expected results: Padding has a limit and the results show correct Padding number
Reproducible with versions: 2022.3.66f1, 6000.0.58f1, 6000.1.16f1, 6000.2.5f1, 6000.3.0b2
Tested on (OS): macOS Silicon Sequoia 15.6.1
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
- Scene view Flythrough mode icon is stuck when maximising the Scene view with a shortcut during the Flythrough mode
- Text highlighting in Package Manager descriptions stays active when right-click is performed while holding the left mouse button down
- Some Material Overrides are viewed as broken when using the Shadergraph CustomLighting package sample
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
Resolution Note:
It's a legitimate bug but falls below the threshold for us to fix in the foreseeable future. Note, in general, the Font Asset Creator window is very low priority for us to improve, and that unfortunately includes minor fixes like this one. We will of course fix major issues like crashes.
Also, the Font Asset Creator window will be significantly when we remove TextCore and switch everyone to ATG.
Resolution Note (6000.3.X):
It's a legitimate bug but falls below the threshold for us to fix in the foreseeable future. Note, in general, the Font Asset Creator window is very low priority for us to improve, and that unfortunately includes minor fixes like this one. We will of course fix major issues like crashes.
Also, the Font Asset Creator window will be significantly when we remove TextCore and switch everyone to ATG.