Search Issue Tracker
Fixed
Fixed in 2021.3.39f1, 2022.3.30f1, 6000.0.2f1
Votes
1
Found in
2021.3.38f1
2022.3.27f1
6000.0.0f1
Issue ID
UUM-70789
Regression
Yes
MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Scenes/SampleScene“ Scene
3. Build and Run the Project
4. Using the File Explorer, go to and open the Player log file
Expected result: An custom success message is logged “…Layers Match“ in the log file
Actual result: An custom error message is logged “…Layers do not match…“ in the log file, meaning the sorting layer did not get changed
Reproducible with: 2021.3.38f1, 2022.3.27f1, 6000.0.0f1
Not reproducible with: 2021.3.37f1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Comments (1)
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
- UI Text color is incorrect when text is rendered on SubMeshUI
- "Invalid SortingGroup index set in Renderer" errors when making many modifications in same frame
- Crash on GizmoBufferSizeHistory::GetBuffer() when opening a specific scene
- RenderTexture is not initialized when it is set as Material's Texture
- Branch node outputs a random value instead of a constant on the false conditon
ASDF_Games
May 20, 2024 17:18
Happens on iOS as well.