Search Issue Tracker
By Design
Votes
0
Found in
Issue ID
1283613
Regression
No
[UX] GameObject has empty layer if the layer it had previously was erased
To reproduce:
1. Open any project
2. Create a new layer
3. Assign the layer to any game object
4. Go to Tags & Layers and erase the newly created layer
5. Select your game object and look at the layer
Expected result: layer mask gets back to Default (or any other default value)
Actual result: layer name is empty, no layer is marked as active in the layer dropdown
Reproduced on: 2019.4.12f1, 2020.1.9f1, 2020.2.0b7
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
- Crash on RenderBufferManager::Textures::GetTempBuffer when rendering a specific scene
- The Inspector header is incorrectly displayed when scripts are recompiled while a Scriptable Object instance is selected
- NullReferenceException is thrown when overriding the UxmlObjectReferences in template instances
- Shaders created with Shader Graph generate a large amount of shader variants and cause slow build times when using a baked lightmap in BIRP
- Shader Graph Matrix property produces random output values when SRP Batcher is enabled
Resolution Note:
Current behaviour doesn't break project in cases where layer gets removed by accident or unintentionally (either locally, or when pulling layer removal from vcs) - if layer is removed adding it back to layer list is all that's needed. With proposed behaviour it would require reassigning layer back to all objects that previously had it.