Search Issue Tracker
Fixed
Fixed in 3.2.x
Votes
0
Found in [Package]
3.2.x
Issue ID
TMPB-191
Regression
No
Text is masked when the Maskable property is disabled
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Open the “Assets/Scenes/SampleScene.unity” Scene
3. Select Text_CLAIM GameObject (Canvas > Scroll View > Viewport > Content > GameObject > button_Claim_Arrow > Button > HitBox > Graphics > Text_CLAIM)
4. In the Inspector Window, under the “TextMeshPro - Text (UI)” select “Extra Settings”
5. Observe that the “Maskable” property is disabled
6. Enter the Play Mode
7. Observe the Game View
Expected result: The text, inside the moving UI element, is not masked when it passes the middle of the screen
Actual result: The text, inside the moving UI element, is masked when it passes the middle of the screen
Reproducible with: 3.0.6, 3.2.0-pre.4 (2020.3.48f1, 2021.3.25f1, 2022.2.20f1, 2023.1.0b17, 2023.2.0a15), 4.0.0-pre.2 (2022.2.20f1, 2023.1.0b17)
Could not test with: 4.0.0-pre.2 (2022.2.20f1 (Text is not visible inside the UI element), 2023.2.0a15 (Multiple “error CS0122” errors))
Reproducible on: Intel MacOS 13.3.1
Note: Disabling and reenabling the “Maskable” property results in the expected behavior
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
- Animator Controller throws MissingReferenceException after undoing Layer Creation
- Full stack trace is always printed when an exception occurs in an IL2CPP build
- Licensing Client fails to launch when opening Unity Hub (licensing client path is not found)
- Licensing Client fails to launch when opening Unity Hub
- Different custom Shader behavior when GPU Resident Drawer is enabled
Resolution Note (fix version 3.2.x):
Maskable now propagates to SubMesh