Search Issue Tracker
Fixed
Votes
43
Found in
4.6.0b17
Issue ID
636209
Regression
Yes
UI: Nested masks behave incorrectly
To reproduce this bug:
1. Open the attached project
2. Open 'MaskingBug' scene
3. It has 3 images with Masks as children of one another and text as a last child
4. Observe the scene
5. The text cannot be seen on b19
6. Open the same scene with b18
7. Notice that text can now be seen in the scene
Comments (17)
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Mortennobel
Sep 19, 2015 13:10
I just ran into a similar problem in my project. It seem to only happen when soft particles in the quality settings is off. So an easy fix is to enable soft particles for all quality levels.
sam_bender
Aug 12, 2015 22:12
I was still having this problem on 5.1.1f1 but after upgrading it appears to be fixed in 5.1.2f1.
Techips
Jul 15, 2015 00:34
I have this issue in 5.1.1f1
Gamba
Jun 24, 2015 18:47
I'm seeing this on 4.6.6p3 on iOS
Razouille
Jun 23, 2015 14:26
I still got this issue in Unity 5.1.1f1 ...
Caiuse
Jun 10, 2015 15:35
This bug has repaired in 5.1.0f3 nested masks cause all elements inside to not draw.
Tyrannicus100BC
Jun 04, 2015 19:35
This is happening again in 5.0.2f1.
Can we get an official comment on this?
dooub_unity_1
May 18, 2015 09:36
This is shown again 4.6.5f1.
theiss
Apr 02, 2015 16:54
WOOOOOHOOOOOOO!!!! Fixed in 4.6.4p1. <happy dance!>
theiss
Mar 31, 2015 13:54
Is this fixed in 5.x only? Bug still exists in 4.6.4f1.