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
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 1.4.0):
I revised the handling of the bounds of the mesh as suggested.