Search Issue Tracker
Fixed
Fixed in 2022.2.7f1, 2023.1.0b10, 2023.2.0a1
Votes
0
Found in
2022.2.0b8
2023.1.0a10
2023.2.0a1
Issue ID
UUM-14307
Regression
Yes
[URP] "Rendering Layers" field gets set to "Nothing" when earlier it was set to "Everything"
How to reproduce:
1. Open the user’s attached “20220905)urp” project
2. Open the “SampleScene” Scene
3. Select the “Directional Light” GameObject in Hierarchy
4. Set “Light (Component) → Rendering Layers” to “Everything”
5. Re-select the GameObject
Expected result: “Rendering Layers” is set to “Everything”
Actual result: “Rendering Layers” is set to “Nothing”
Reproducible with: 14.0.3 (2022.2.0b2, 2022.2.0b8), 15.0.1 (2023.1.0a10)
Not reproducible with: 12.1.7 (2021.3.9f1), 13.1.8 (2022.1.16f1), 14.0.3 (2022.2.0b1)
Couldn’t test with: 10.10.0 (2020.3.39f1) (not featured)
Reproduced on: macOS 12.5 (Intel), Windows 10
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
- MultiColumnTreeView does not auto-expand foldouts when autoExpand is set to "true"
- Animation does not control the property of the Gameobject when the keyframe and initial value are the same
- Decal Technique set to Automatic prefers the DBuffer option when using OpenGL
- Brush Size in the Inspector window does not update when the Brush Size in Scene View is changed
- "ArgumentOutOfRangeException" errors are thrown every time a keyboard key is pressed when renaming a component in UI Builder with a symbol and changing the name after label attribute warning
Resolution Note (fix version 2023.2.0a1):
Fixed in 2023.2.0a1
Resolution Note (fix version 2023.1.0b10):
Fixed in 2023.1.0b10
Resolution Note (fix version 2022.2.7f1):
Fixed in 2022.2.7f1