Search Issue Tracker

Active

Under Consideration for 6000.6.X

Votes

0

Found in

6000.0.71f1

6000.3.11f1

6000.4.0f1

6000.5.0a9

6000.6.0a1

Issue ID

UUM-137866

Regression

No

Glyph Adjustment Table is modified when using an existing TMP Font Atlas to generate a new TMP Font Atlas with the same settings

Text (TextMeshPro)

-

How to reproduce:
1. Open the attached “IN-137132“ project
2. In the Project window, open the “Original” folder (Assets > Fonts > Original)
3. Double-click “Oswald-SemiBold SDF“
4. In the Inspector, note the Glyph Adjustment Table’s “Records” count
5. In the Inspector, select Update Atlas Texture
6. In the Font Asset Creator window, click “Generate Font Atlas” and save the Font Atlas as “Regenerated“
7. Locate and double-click the “Regenerated“ Font Asset, repeat step 4

Actual result: The “Regenerated“ Font Atlas’s Glyph Adjustment Table “Records“ count is different from “Oswald-SemiBold SDF’s“
Expected result: The “Regenerated“ Font Atlas’s Glyph Adjustment Table is the same as “Oswald-SemiBold SDF’s“

Reproducible with: 2023.1.0a1, 6000.0.71f1, 6000.3.11f1, 6000.4.0f1, 6000.5.0a9, 6000.6.0a1

Reproducible on: Windows 11
Not reproducible on: No other environments tested

Workaround: Manually edit the Glyph Adjustment Table to remove unwanted kerning from affected symbols

Notes:
- No settings are changed when generating a new Font Atlas
- This issue impacts the spacing between symbols
- Issue reproduces in 2023.1.0a1, but instead of there being more “Records“ after generating a new Font Atlas, there are 0

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.