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
- The Player renders black on a Quest headset when MSAA, Post Processing, and Spacewarm depth submission are enabled
- Graphics Compositor breaks Unity rendering when the "Output Camera" is changed to a scene Camera and one Camera SubLayer is active
- The Editor freezes on RenderGraphViewer.Repaint when entering too many characters in search fields without character limits
- Adding a new SubLayer in Graphics Compositor renders BaseLayer darker and makes it flicker
- DOTS Materials Not Rendering in Player When Using Entity Graphics with Custom SRP
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