Search Issue Tracker
Fixed in 1.5.0-preview.9, 2.1.0-preview.9, 3.0.0-preview.9
Votes
1
Found in [Package]
1.1.0
Issue ID
1218526
Regression
No
[TextMeshPro] useMaxVisibleDescender returns true when set to false
Reproduction steps:
1. Open the attached project "case_1218526-TextmeshProBug2.zip"
2. Enter Play Mode
3. Observe the Console window messages
Expected result: useMaxVisibleDescender is set to false through the "TextmeshProBug.cs" script
Actual result: useMaxVisibleDescender state remains true even after changing it through script
Reproduces on: 2018.4.17f1, 2019.3.1f1, 2020.1.0a23
Could not test with 2017.4 due to the package not existing
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 1.5.0-preview.9, 2.1.0-preview.9, 3.0.0-preview.9):
This issue has been resolved. The fix will be included in the next release of the TMP package which will be version 1.5.0-preview.9 for Unity 2018.4, version 2.1.0-preview.9 for Unity 2019.x and 3.0.0-preview.9 for Unity 2020.x