Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.1.X, 6000.2.X
Votes
1
Found in
6000.0.44f1
6000.1.0b12
6000.2.0a8
Issue ID
UUM-101484
Regression
Yes
"Font Asset Creator - Error Code [Invalid_File]..." error message is displayed when generating Font Atlas
Reproduction steps:
1. Open the attached “TMProBoldBug.zip” project
2. Select the “Assets/TextMesh Pro/Resources/Fonts & Materials/Latin/Aller-Light.asset“ Font asset
3. Click the “Update Atlas Texture” button in the Inspector window
4. Click the “Generate Font Atlas” button in the Font Asset Creator window
5. Observe the Console and Font Asset Creator window
Expected result: “Font Atlas generation completed” message is displayed and the Font asset is generated
Actual result: “Font Asset Creator - Error Code [Invalid_File] has occurred trying to load the [Aller-Light] font file. “ error message is displayed and the Font asset is not generated
Reproducible with: 3.2.0-pre.1, 3.2.0-pre.12 (2022.3.60f1), (Built-in) 6000.0.44f1, 6000.1.0b12, 6000.2.0a8
Not reproducible with: 3.0.9 (2022.3.60f1)
Couldn't test with: 4.0.0-pre.1 (2022.3.60f1) error “CS0029: Cannot implicitly convert type 'uint[]' to 'int[]'“, 4.0.0-pre.2 (2022.3.60f1) warnings “Font Asset was not found”
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Comments (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
- Manual reference page for Grid Selection is missing
- Awaitable.NextFrameAsync causes GC Alloc 0.7 KB when using CancellationToken
- Prefab "Overrides" list item popups are overridden when navigating with keyboard arrow keys
- Alpha Tolerance setting does not affect generated outlines when generating Custom Physics Shape in the Sprite Editor
- The information/help message section misses a margin in the "Profiler" window
tessellation
Mar 27, 2025 18:02
If you check "Include Font Data" then it works. However, in earlier versions of Unity/TMPro, you did not have to include font data to generate font atlases. This is the proper behaviour because OTF/TTF font data is not required for FontAssets that use only pre-generated atlases.