Search Issue Tracker
By Design
Votes
1
Found in
2017.4.0f1
2018.3.0a1
2019.1.0a1
2019.1.14f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
Issue ID
1177636
Regression
No
Cannot change the font size of Text Mesh to zero when using a non-dynamic font
How to reproduce:
1. Open user's attached project ("BugDemo.zip") using the EnvIronman VM (more information in Edit)
2. Open the sample scene
3. Select the New Text GameObject in the Hierarchy
4. Change the Font Size field to 0 and press enter
Expected result: The Font Size field is set to 0
Actual result: The Font Size field is set to 1
Reproducible with: 2017.4.32f1, 2018.4.7f1, 2019.1.14f1, 2019.2.2f1, 2019.3.0a12, 2020.1.0a1
Notes:
The issue is more severe as changing the Text field of the Text Mesh component will throw Console warnings if the Font Size is not 0.
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:
The Legacy TextMesh component has always had this limitation where the font must be set to Dynamic to enable changing the point size. When the font is set to Unicode or other modes, the only point size available is the point size specified in the Font Importer.
This behavior is by design and we strongly recommend the user migrate to TextMesh Pro which provides all the functionality of the legacy TextMesh and much more.