Search Issue Tracker
Fixed in 1.5.0-preview.3 & 2.1.0-preview.3
Votes
0
Found in [Package]
1.2.4, preview.1 - 3.0.0
Issue ID
1191793
Regression
No
Default TMP presets are not used when adding TextMeshPro GameObjects via the right-click context menu
How to reproduce:
1. Create a new Unity project
2. Create any TextMeshPro GameObject via the right-click context menu in the Hierarchy window
3. Make some changes to the main component(e.g. 'Interactable' for a button) and save the preset
4. Set the newly generated preset as the default preset
5. Right-Click in the Hierarchy window and create the same TextMeshPro GameObject
Expected result: the new GameObject's TMP Component uses the new default preset
Actual result: the new GameObject's TMP Component does not use the new default preset
Reproducible with: 2018.4.13f1, 2019.2.14f1, 2019.3.0f1, 2020.1.0a15
Could not test with: 2017.4.35f1(presets not yet implemented)
Reproducible with package versions: 1.2.4, preview.1 - 3.0.0
Notes:
Adding a Component via the 'Add Component' menu works as expected and uses the new default preset
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
- [Android] The Player freezes when disabling Bluetooth while connected to the headphones
- Addressable bundles are not retrieved from the cache when a WebGL Player is refreshed
- Sprites are incorrectly occluded by Sprite Physics Shape culling when behind in sorting order
- CPU usage is increased when the Editor is idle with the ProBuilder Package installed
- Unstable lighting when additional light sources are added in Shader Graph nodes
Resolution Note (fix version 1.5.0-preview.3 & 2.1.0-preview.3):
Added support for Unity Presets in the Editor for both <TextMeshPro> and <TextMeshProUGUI> components. This new functionality will be available in the next TMP package release which will be version 1.5.0-preview.3 for Unity 2018.4 and 2.1.0-preview.3 for Unity 2019.x