Search Issue Tracker
By Design
Votes
1
Found in
2021.3.47f1
2022.3.55f1
6000.0.33f1
6000.1.0b1
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-92420
Regression
No
TextMeshPro calculates Width Compression incorrectly when using certain values in the WD% field
Reproduction steps:
1. Open the attached “TMP Bug.zip” project
2. Open the “SampleScene”
3. Select “SampleText” GameObject from the Hierarchy
4. In the TMP Component find the “Auto Size Option” property and the “WD%” field
5. In the “WD%” field input value of “18”
6. Observe the Game view
7. Now in the “WD%” field input value of “19”
8. Observe the Game view again
Expected result: The text stays inside the container
Actual result: The text overflows from the container and “Auto Size Iteration Count: 100. Final Point Size: 30” log is visible in the Console
Reproducible with: 2021.3.47f1, 2022.3.55f1, 6000.0.33f1, 6000.1.0b1
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environment tested
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
There is max number of iterations for this feature which is set to 100.
This maximum iteration is set in the TMP_Text.cs file as follows:
protected int m_AutoSizeMaxIterationCount = 100;
This value could be increased to allow for more iterations. Please note increasing this number will add additional performance overhead for those additional iterations.