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
- OnPreviewSettings() not invoked when Inspector shows two ObjectPreviews for the same object
- Assertion fails when creating a TextMeshPro Prefab with Asset Transformer Toolkit (Pixyz) installed
- Help button leads to a missing documentation page when clicked on a TMP_Font Asset in the Inspector
- Background Image type reverts to Texture when changed and the VisualElement is reselected in UI Builder
- "Do not use ReadObjectThreaded on scene objects!" repeatedly printed to the Editor log when attempting to open a specific project
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