Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
2.2.0-preview.3
3.2.0-pre.3
Issue ID
TMPB-1
Regression
No
[TMP] Text with Rich Text Material tag is not displayed properly when using Dynamic Font Atlas and Asset Bundles
How to reproduce:
1. Open project "Test.zip"
2. Delete "assetBundles" folder from the root project folder
3. Build Asset Bundles (in Menu bar go to Assets > AssetBundles > Build AssetBundles)
4. Build and Run on Android or iOS
5. Observe the upper text
Expected result: Text is which is displayed: Update X3
Actual result: Text which is displayed: Update
Reproducible with: 2.2.0-preview.3 (2019.4.38f1), 3.2.0-pre.3 (2020.3.33f1, 2021.3.0f1)
Could not test with: 3.2.0-pre.3, 4.0.0-pre.1 (2022.1.0b16, 2022.2.0a11) (issues when building Asset Bundles)
Notes:
- Only one "Update" text will be displayed on Android devices if steps are done incorrectly
- The issue does not reproduce in Editor, can be reproduced on Android and iOS
- 3 different issues can be spotted in this case:
1) If the text doesn't exist in the build Scene at all (no text component), the rich text part is completely white
2) If the text exists in the build Scene but doesn't contain the characters in the rich text part, the rich text part is transparent (this is reproduced by following steps without changing Scene)
3) If the text exists in the build Scene and also contains all characters you need in the rich text part, it displays correctly
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Thank you for bringing this issue to our attention. After careful consideration, we have determined that this issue is not aligned with our current development priorities and focus areas (UI Toolkit). As such, we have decided not to invest time and resources into addressing it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.