Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2019.4
2020.3
2020.3.3f1
2021.2
2022.1
2022.2
Issue ID
1385838
Regression
No
Rendering order of Canvas depends on a child's Z position when Render Mode is "Screen Space - Camera"
Reproduction steps:
1. Open the user's attached project "CanvasSortingBug.zip"
2. Open "SampleScene"
3. Select "RogueImage" under "Canvas1 (Plane Distance 10)" GameObject in the Hierarchy window
4. Enable the Image component in the Inspector window
Expected result: The rendering order is determined by Plane Distance, the red square stays in front of other squares
Actual result: The Canvas and its child GameObjects are rendered behind the other Canvases, the red square is behind other squares
Reproducible with: 2019.4.36f1, 2020.3.29f1, 2021.2.12f1, 2022.1.0b9, 2022.2.0a5
Notes:
1. Plane Distance still affects the rendering order when the Image component is enabled
2. Reproducible with Image and Raw Image components
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 2022.2):
Fixing issue where a rouge image would increase the AABB of the canvas causing its center of rendering to potentially be off shifted from the distance it should be rendered
Fixed in: 2022.2.0a9