Search Issue Tracker
Fixed
Fixed in 1.3.2, 1.4.2
Votes
2
Found in [Package]
1.3.1
1.3.2
Issue ID
LOC-727
Regression
Yes
Error when use TextMeshPro Font Assets with Localized Property Variants
1. Install Localization and create 2 locale: eng (en) and thai (th)
2. Create 2 Localization tables: AssetTable: assets and StringTable: texts
3. Create 1 UI TextMeshPro
4. Use Localization Scene Control to change Text and Font Asset for UI TextMeshPro.
5. In Addressables Group > Play Mode Script > Use Existing Build
6. In Addressables Group > Build > New Build > Default Build Script
And when Click Play On Editor, i change language and got error.
* If i only change text and don't change Font Asset for TextMeshPro. It will work without error.
* If i use Unity Localization v1.1.1, v1.2.1, and change both text and Font Asset for TextMeshPro. It will work without error.
So i think this is error for Unity Localization v1.3.1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
Add comment