Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.18f1
2023.2.6f1
2023.3.0b3
6000.1.0a7
6000.2.0a1
Issue ID
UUM-61453
Regression
No
[TextMeshPro] TMP_FontAsset includes Creation Settings -> Character Sequence in builds
The field Character Sequence which is used to generate the FontAsset in the FontAsset Creator Window is being included in builds and leads to redundant string allocations at runtime. Customers are likely to use their entire localization tables as input when creating FontAssets, which adds up to megabytes of redundant memory usage.
Affects all versions
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:
After careful consideration, we have decided not to fix this issue. In future versions, the way creation settings work will be changed, eliminating any memory impact.
For the current version, as a workaround, you can remove it manually by going to Inspector > Debug Mode > Delete Character Sequence.