Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.4.X
Votes
2
Found in
2018.4
2019.3.7f1
2020.2
Issue ID
1251717
Regression
No
Current scene is not dirtied, other scenes are not updated when rearranging in-use sorting layers
Reproduction steps:
1. Open attached project "SortingLayerUpdate.zip" and create a new scene
2. In Project window, select "Prefab"
3. In Inspector window, go to Sprite Renderer -> Sorting Layer -> Add Sorting Layer...
4. Create a new Sorting Layer
5. Slot the newly created Sorting Layer between the "3" and "4" layers
6. In the Sprite Renderer of the Prefab, set the Sorting Layer to the new Sorting Layer
7. Save the project to update the Prefab
8. Open "Third Scene"
9. You should see a check mark in a red box.
Expected: Check mark in a red box
Actual: Red box
Note:
Without the fix, selecting the 4th Layer GameObject, and disabling and enabling the Sorting Group will give the expected result
Using the user's project and reproduction steps should not result in any scene differences for Gameplay scene.
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
- The cursor moves into wrong place when renaming folder/asset
- Assertion error "(dx - width < padding) || (dy - height < padding)" when using Pack Preview
- [Memory Profiler] The EntryType.NativeAllocationSites_MemoryLabelIndex of snapshots only reports -1 or 0 instead of the MemLabel used for allocations made from any call site.
- [Vulkan] Artifacts appear in the Player when using Screen Space shadows with orthographic camera
- Errors OnGUIDepth changed & GUIUtility:ProcessEvent when opening Textures with Third Party App
Resolution Note (fix version 2020.1):
Fixed in 2020.2.0a16
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b16
Resolution Note (fix version 2019.4):
Fixed in 2019.4.5f1