Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2019.4.29f1
2020.3
2021.1
2021.2
2022.1
Issue ID
1356035
Regression
No
Tilemaps ignores Order of Layers until you enter to Play
To reproduce:
1. Download the attached "TileLayerBug.zip" project and open in Unity
2. Open "Unity_Office_4th_Floor2" scene
3. Select "Floor" gameObject and observe that its Order in Layer is 0
4. Duplicate "Floor" gameObject and paint some Tiles on it
5. Observe that those Tiles are shown in Scene and Game windows
6. Enter Play mode
7. Observe that tiles that were painted on a duplicate of the "Floor" gameObject vanished
Expected results: Unity Editor should respect Order in Layers in Edit mode
Actual result: Unity Editor ignores Order in Layers until you enter Play Mode
Notes:
- This issue should appear on both Windows and macOS
- This might be not a Package bug but a Unity Editor bug
Reproduced on Unity 2019.4.29f1, 2020.3.16f1, 2021.1.17f1, 2021.2.0b7 and 2022.1.0a5
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
- A Console error is not handled correctly when using #pragma kernel with the Kernel name not provided
- L(a,b) expression in float fields has erratic behaviour when ordering due to using instanceID as an index
- SubMesh GameObject duplicates and warning is logged to console when trying to undo failed deletion
- InvalidOperationException is thrown when switching to a custom Debug Draw Mode in Scene View
- [Android][Vulkan] Skybox and Environment effects flicker in the Player when using the Vulkan Graphics API
Resolution Note:
In this case the editor is respecting Order in Layers. Tilemaps with the same sorting layers and order in layer will be sorted by a tiebreaker in the system depending on the render queue which may not be the same in Edit and Play mode
The rules for sorting for 2D Renderers can be found here: https://docs.unity3d.com/Manual/2DSorting.html