Search Issue Tracker
Fixed in 1.5.2, 2.1.2, 3.0.2
Votes
0
Found in [Package]
1.5.0-preview.10
Issue ID
1285499
Regression
Yes
Incorrect values are returned when calling TextMeshProGUI.GetPreferredValues more than once
How to reproduce:
1. Open the user's attached "TMP Bug.zip" project
2. Open the "SampleScene" Scene
3. Enter Play Mode
4. Observe the Console log
Expected result: "Second call to get preferred values:(146.9, 40.2)" message is printed in the Console log (GetPreferredValues returns correct values)
Actual result:" Second call to get preferred values:(0.0, 0.0)" message is printed in the Console log (GetPreferredValues returns incorrect values)
Reproducible with: 1.5.0-preview.10, 1.5.1 (2018.4.28f1), 2.1.1 (2019.4.13f1), 3.0.1 (2020.1.11f1, 2020.2.0b9, 2021.1.0a2)
Not reproducible with: 1.41, 1.5.0-preview.8 (2018.4.28f1)
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
- UI Source Image property gets set to 'None' when using a specific Sprite and Play mode is entered
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
Resolution Note (fix version 1.5.2, 2.1.2, 3.0.2):
Fixed in: 3.0.3, 2.1.3, 1.5.3