Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.2f1
2019.1.0a1
2019.2.0a1
Issue ID
1145457
Regression
No
Sub-canvas with "Override Sorting" enabled is not rendered after disabling the parent Canvas and entering Play mode
How to reproduce:
1. Open attached project "toggle-root-canvas.zip" and scene "toggle-root-canvas"
2. In the Hierarchy window, select parent "Canvas" object
3. In the Inspector window, observe that "Canvas" component is disabled
4. In the Hierarchy window, select child "Canvas" object
5. In the Inspector window, observe that "Canvas" component is enabled and "Override Sorting" is enabled (the issue - child Canvas should be rendered/visible)
6. Enter Play mode (neither red or white cube is visible)
7. In Game View, press on "Toggle" button to enable the parent "Canvas" component
8. In Game View, press on "Toggle" button again to disable the parent "Canvas" component
Expected result: in the Game View, the red cube is always visible
Actual result: The red cube is only visible when enabling and disabling parent Canvas
Reproducible with: 2017.4.24f1, 2018.3.13f1, 2019.1.0f2, 2019.2.0a11
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
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- “UnityException: GetInvalidFilenameChars” errors are thrown, and the Overlay Save Preset button becomes unusable when entering Play Mode with a shortcut while Overlay Save Preset window is opened
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
Resolution Note (2019.3.X):
Low priority defect for the moment. This bug is unlikely to be fixed in the near future.