Search Issue Tracker
Fixed in 3.2.0-pre.2
Votes
0
Found in [Package]
3.0.6
Issue ID
1381874
Regression
Yes
Visual Studio compiler warnings when building a new project with most recent TextMeshPro Package in 2021.2
How to reproduce:
1. Create a new empty project
2. Change External Script Editor to Visual Studio for Mac (Unity -> Preferences -> External Tools)
3. Turn on "Registry Packages" and "Built-in Packages"
4. Press "Regenerate project files"
5. Create a new C# script and open it
6. Build the script (Build -> Build All)
7. Open the Errors window (Bottom Right of the Window)
Expected results: No errors or warnings
Actual results: TMP_FontAsset.cs, TMP_FontAssetCreatorWindow.cs and UwpPlatformSetup.cs has "Obsolete" code
Reproducible with: 3.0.6 (2021.2.0a10, 2021.2.8f1)
Not reproducible with: 2.1.6 (2019.4.34f1), 3.0.5 (2020.3.25f1, 2021.2.8f1), 3.0.6 (2020.3.25f1, 2021.2.0a9, 2022.1.0b2)
Note:
- It would seem that after testing this issue is purely happening in 2021.2
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 3.2.0-pre.2):
Fixed in: 3.2.0-pre.2