Search Issue Tracker
In Progress
Under Consideration for 2021.3.X, 2022.3.X
Votes
0
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [VFX] Custom HLSL with 'int' parameter, without the 'in/out/inout' access modifier is not supported
- [Windows] Lens Flare doesn't work in the Lens Flare Showroom URP Sample Scene
- Crash on ujob_execute_job while using OverlapBoxCommand when collisions are more than maxHits
- The validity of the multiple handles can behave differently based on the load/release operations order, when multiple Addressables.LoadAssetAsync and Addressables.Release are used to load and release the same Addressable Asset
- Dynamic text is rendered in the background when it is inside the <font> tag
Add comment