Search Issue Tracker
Won't Fix
Votes
0
Found in
5.1.1f1
Issue ID
713497
Regression
No
[Canvas] Canvases rendering order doesn't depend on their positions in hierarchy
Steps to reproduce:
1. Open attached project
2. Open scene 'TestScene'
3. Run it and notice that two canvas objects ('testCanvas1' and 'testCanvas2') are created and only testCanvas1 is visible
4. Change their position in hierarchy and notice that rendering order stays the same
5. Disable and enable testCanvas2 and notice that now it's rendered on top of the testCanvas1
Workaround: Sort order can be used as a workaround
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment