Search Issue Tracker
Fixed in 1.4.0
Votes
0
Found in [Package]
1.3.0
Issue ID
1093388
Regression
No
[Text Mesh Pro] Incorrect mesh bounds are assigned when text field is empty
To reproduce:
1. Ope attached project "UnityTest.zip"
2. Enter play mode
3. Observe the console
Expected: mesh bounds calculated correctly when providing empty text field
Actual: mesh bounds are not updated when text field is empty, also incorrect default bounds are assigned upon initialization (1920,0,1080)
Reproduced in: 2017.4.15f1, 2018.2.15f1, 2018.3.0b9, 2019.1.0a8
Note: if needed, observing the process frame by frame when pausing Play mode could be helpful
Comments (1)
-
TrueNoob141
Apr 29, 2019 12:30
Still have in 1.4.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 (fix version 1.4.0):
I revised the handling of the bounds of the mesh as suggested.