Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.46f1
2022.3.54f1
6000.0.31f1
6000.1.0a8
Issue ID
UUM-90580
Regression
No
Different font across Remapping and Conversion tools
How to reproduce:
1. Create a new Unity project and import TextMeshPro
2. Go to Window -> TextMeshPro -> Project Files GUID Remapping Tool
3. Go to Window -> TextMeshPro -> Project Text Spacing Conversion Tool
4. Simultaneously focus the both windows
5. Observe the "Project Scan Results" fields
Expected results: The windows use the same font
Actual results: The windows use the different font
Reproducible with: 2021.3.46f1, 2022.3.54f1, 6000.0.31f1, 6000.1.0a8
Reproducible on: macOS Sequoia 15.0
Not reproducible on: No other environment tested
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:
We are unable to address minor cosmetic issues like this in TMP. It's not worth the risk to introducing regressions.