Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2.1.6
3.2.0-pre.2
Issue ID
TMPB-21
Regression
No
TextMeshPro text is visible for 1 frame regardless of RectMask2D when enabling Text Component
How to reproduce:
1. Open the user's attached project
2. Open scene Scenes/SampleScene
3. Press the Play button
4. In the Hierarchy window, select the GameObject "TextName" (under Canvas -> MaskIssue -> TextMask)
5. In the Inspector view, disable and re-enable the checkbox next to the TextMeshPro - Text (UI) Component
6. Observe the Game view while performing step 5
Expected result: no text is visible in the Game view
Actual result: the text "Droppod name" is visible for one frame in the Game view after the GameObject has been re-enabled
Reproducible with: 2.1.6 (2019.4.32f1), 3.0.6, 3.2.0-pre.2 (2020.3.23f1, 2021.1.28f1, 2021.2.3f1, 2022.1.0a15)
Notes:
1. With TextMeshPro 2.1.6 (2019.4.32f1), the text stays permanently visible when the GameObject is re-enabled
2. On some versions, it takes several repeated attempts to notice the text becoming visible for one frame
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
- Memory leak occurs when focused on Player while using Direct3D12
- 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
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.