Search Issue Tracker
Fixed
Votes
1
Found in
2021.3.33f1
Issue ID
UUM-57681
Regression
Yes
TextMeshPro package throws multiple Shader errors when importing TMP Essential Resources
How to reproduce:
1. Create a new project with any template
2. Make sure the TextMeshPro package is added to the project (Window > Package Manager > Unity Registry > “TextMeshPro” > “Install”)
3. Import TMP Essential Resources (Window > TextMeshPro > TMP Essential Resources)
4. Observe the Console
Expected result: No errors are thrown
Actual result: Multiple “Shader error in …” errors are thrown
Reproduced with: 2021.3.33f1
Not reproduced with: 2022.3.14f1, 2023.2.3f1, 2023.3.0a17
Reproduced on: macOS 14.1.1 (Intel) (by reporter), Windows 11
Not reproducible on: No other environment tested
Notes:
1. After importing TMP Essential Resources the errors can be ignored and Play Mode can be entered
2. In 2023.2 and 2023.3. streams the TextMeshPro package is no longer available as it was merged into the UGUI package
3. The regressed version is in the TextMeshPro package version → additional information is provided in internal comments
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-12666