Search Issue Tracker
Not Reproducible
Not Reproducible in 2023.3.X
Votes
0
Found in
2022.3.18f1
2023.2.7f1
2023.3.0b4
Issue ID
UUM-62105
Regression
No
[TextMeshPro] Wrong “preferredHeight” is returned when using “CalculatePreferredValues” if having VerticalLayout and “Control Child Size” “Height” enabled
How to reproduce:
1. Open the user’s attached “TMPPreferredHeightBug.7z” project
2. Open “SampleScene” Scene (Assets > Scenes)
3. Enter Play Mode
4. Press the “Reproduce Bug” Button 3 times
5. Observe the result
Expected result: All of the text is higher than the button
Actual result: Some of the text is at the same height as the button
Reproducible with: 3.0.6 (2021.3.34f1), 3.2.0-pre.7 (2022.3.19f1, 2023.2.8f1, 2023.3.0b4
Could not test with: 4.0.0-pre.2 (errors after package upgrade)
Reproduced on: macOS 14.2.1 (Intel)
Not reproducible on: No other environment tested
Note: reproducible in the Editor and Standalone Player (macOS)
Workaround: change “m_internalCharacterInfo[m_characterCount + 1].character” to “m_TextProcessingArray[m_characterCount + 1].unicode” in “TMP_Text.cs”
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:
This potential issue no longer reproduces with the more recent version of TextMesh Pro such as version 3.2.0-pre.12 or the included version of TMP packaged with Unity 6.x.
Most likely this behavior was resolved in previous releases.
Resolution Note (2023.3.X):
This potential issue no longer reproduces with the more recent version of TextMesh Pro such as version 3.2.0-pre.12 or the included version of TMP packaged with Unity 6.x.
Most likely this behavior was resolved in previous releases.