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-117602
Regression
No
Font Asset Creator Font Face does not update when changing Include Font Data in the Font Import Settings
Steps to reproduce:
- Create a new Unity project using the Universal 3D template
- Import the provided Font in the Attachments
- Select the imported Font
- Disable "Include Font Data" in the Inspector window
- Open the Font Asset Creator window (Window > Text > Font Asset Creator)
- Dock the Font Asset Creator window
- Select the imported Font as the Source Font
- Repeat step 3
- Enable "Include Font Data" in the Inspector window
- Observe the Font Face in the Font Asset Creator window
Actual results: The Font Face dropdown is still empty and not interactable
Expected results: The Font Face dropdown is interactable
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
Notes:
- Font Face updates only when the Font Asset Creator window is reopened
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.