Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.7f1
2019.1.0a1
2019.2.0a1
Issue ID
1138914
Regression
No
Sort Order is not respected for a newly created Canvas until Play Mode is entered or any adjustments are made
How to reproduce:
1. Open user-submitted project (SortOrderTests) and 'SampleScene' scene
2. See that the Sort Order of the Canvas GameObject is set to 100
3. Create a new Canvas GameObject
4. Add a UI > Image GameObject to the new Canvas
Expected result: the new Image is rendered behind the existing one
Actual result: the new Image is rendered in front of the existing one
Reproducible with: 2017.4.23f1, 2018.3.10f1, 2019.1.0b8, 2019.2.0a9
Notes:
Changing any of the Canvas Component settings for the newer Canvas GameObject or entering Play Mode fixes the incorrect sorting order
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment