Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
1
Found in
2020.3.45f1
2021.3.18f1
2022.2.6f1
2023.1.0b3
2023.2.0a1
Issue ID
UUM-26611
Regression
No
Canvas Override Sorting breaks sorting order when it is disabled and enabled again
Reproduction steps:
1. Open the attached “bug-report.zip“ project
2. Open “SampleScene” scene
3. Enable Override Sorting in “CanvasOverride” GameObject
4. Enter Play mode
5. Disable and enable Override Sorting in “CanvasOverride” GameObject
6. Observe the Game window
Expected result: Button reappears when Override Sorting is enabled again
Actual result: Button and Images disappear when Override Sorting is enabled again
Reproducible with: 2020.3.45f1, 2021.3.18f1, 2022.2.6f1, 2023.1.0b3, 2023.2.0a1
Reproduced on: macOS Monterey 12.6 (Intel)
Note: Reproducible on a new project but inconsistently
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
- 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
Resolution Note:
Although we understand this is a bug, by using proper values for "Order in Layer" guarantees a problem won't happen. After investigation we have deemed this a low priority issue that won't be fixed in the near future either because it is too costly to implement or because there are risks of introducing other problems doing so.
If you feel this is a wrong assessment please reach out again, providing more details about the impact of this issue.
Resolution Note (2023.2.X):
Although we understand this is a bug, by using proper values for "Order in Layer" guarantees a problem won't happen. After investigation we have deemed this a low priority issue that won't be fixed in the near future either because it is too costly to implement or because there are risks of introducing other problems doing so.
If you feel this is a wrong assessment please reach out again, providing more details about the impact of this issue.