Search Issue Tracker
Won't Fix
Won't Fix in 6000.4.X
Votes
0
Found in
6000.3.0b3
6000.4.0a1
Issue ID
UUM-120129
Regression
Yes
”Font face is not created” error is thrown and when closing Font Asset Creator
Reproduction steps:
1. Create a new project
2. Import TMP Essential Resources (Window > TextMeshPro > Import TMP Essential Resources)
3. Open Search window
4. Type “font” in the search bar and open Font Asset Creator window by double-clicking one of the search results
5. Change some of the fields Font Asset Creator window and close it
6. Observe Console and Search windows
Actual result: ”Font face is not created.
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)” error is thrown
Expected result: No errors or warnings are thrown
Reproducible with: 6000.3.0b1, 6000.3.0b3, 6000.4.0a1
Not reproducible with: 2021.3.56f1, 2022.3.67f1, 6000.0.58f1, 6000.2.6f1, 6000.3.0a6
Reproduced on: macOS Sequoia 15.4 (M4)
Note:
- Issue is not consistently reproduced, steps 4-6 might need to be repeated a few times
- Issue is reproducible on Text and TextMeshPro Font Asset Creators
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Resolution Note:
We'd love to fix this but it's unfortunately too minor for us to get to in a reasonable amount of time. It's a corner case that so far few users have run into and there are no negative consequences. We might re-open the bug in the future.
Resolution Note (6000.4.X):
We'd love to fix this but it's unfortunately too minor for us to get to in a reasonable amount of time. It's a corner case that so far few users have run into and there are no negative consequences. We might re-open the bug in the future.