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
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
- Frame Debugger Target Selection Search Results window becomes too tiny to even see the default “Editor” selection when there are no search results
- Async method in Play Mode being aborted when calling `new System.Windows.Forms.Form`
- Animator window Eye button on click visual does not cover the whole area of the button when clicked
Resolution Note (fix version 1.4.0):
I revised the handling of the bounds of the mesh as suggested.