Search Issue Tracker
Fixed in 2017.1.0f3
Votes
3
Found in
5.6.0f2
Issue ID
896778
Regression
Yes
Child Canvas elements are not rendered after disabling and re-enabling parent Canvas
How to reproduce:
1. Open the attached "CanvasInCanvas" project and open "CanvasProblem" scene
2. Enter playmode
3. Press "Toggle other canvas" button twice
Expected result: Canvases are disabled, when re-enabled and all of their elements are rendered to screen
Actual result: Canvases are disabled, when re-enabled and child Canvas elements are not rendered to screen
Regression introduced in - 5.6.0f1
Reproducible with - 2017.1.0a5, 5.6.0f3, 5.6.0f1
Not reproducible with - 5.6.0b11, 5.5.2p3
Notes:
1. The issue can be reproduced without entering playmode, just disable "ParentCanvas" in the Inspector and re-enable it
2. Entering and exiting playmode fixes the issue
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
- Object references are not loaded after you git checkout to another branch
- Only one of multiple copies of the same StateMachineBehaviour script is visible when added to the Animation state
- [XR][Vulkan][Oculus] Crash in hybrid renderer BeginRenderPass
- [Mobile]Dynamic batching is not working when working with sub mesh on a mobile device
- [Hub] Warning pop-up contains <strong></strong> when attempting to add a project to the list of projects while it's already open
leni8ec
Nov 28, 2017 16:48
Same Issue in Unity 2017.2.0p1...
taparahmet
Aug 09, 2017 08:13
I've encountered this issue with version 2017.2.0b5.
Please, could you check it?
Thanks.
mishak
Apr 04, 2017 13:16
I found the workaround. I remeber that bug was in one of the older releases. You can fix it by recreating child canvases and saving scene.
Shame on you, Unity!
mishak
Apr 04, 2017 12:30
Please, fix it!