Search Issue Tracker
Active
Under Consideration for 6000.0.X
Votes
1
Found in
2023.2.0a20
2023.3.0a1
7000.0.0a1
Issue ID
UUM-42159
Regression
No
[TextMeshPro] text disappears when only the characters from fallbacks are in the camera viewport
How to reproduce:
1. Open the attached user project “TMPTextBug.zip“
2. Open Scene “Sample_03_TextStyleAssigner”
3. Zoom on to the bottom of the text in the Scene view
Expected result: The text doesn’t disappear
Actual result: The text disappears
Reproducible with: 3.2.0-pre.3, 3.2.0-pre.4 (2020.3.46f1, 2021.3.22f1, 2022.2.12f1, 2023.1.0b9, 2023.2.0a8), 4.0.0-pre.2 (2022.2.12f1, 2023.1.0b9, 2023.2.0a8)
Reproduced on: macOS 13.0.1 (Intel), Windows 10 (by reporter)
Corresponding Slack Thread
Note:
- Not reproducible in Builds
- The mesh renderer of parent and sub-mesh are disabled
- Frustum is based on the bounds of the parent and doesn’t include the sub-mesh bounds, it’s a problem because if there are only fallback’s characters, the parent’s bounds will have a size of zero and the text will always disappear
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
Add comment