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
- Specular lighting visible in a camera with Path Tracing when Preserve specular lighting is disabled in observed material
- Cinemachine package throws CS1061 errors in the Console when installed in a project that has HDRP and URP installed
- Editor.log file size grows rapidly when a scene exceeds the "Maximum Shadow on Screen" limit setting in the HDRP Asset
- Player build freezes after calling Application.Quit() when the scripting backend is set to IL2CPP
- Texture is not applied on a Custom Render Texture when a Cubemap is selected as the texture
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