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
- [2023.2] HDRP Asset Settings Helper throws a NullReferenceException
- [URP] SubmitRenderRequest with NativeRenderPass + Upscaling doesn't work
- “ArgumentOutOfRangeException” error appears when inserting a double character if using “SetValueWithoutNotify” on UI Toolkit’s TextField
- Particle System emission delays between particle generations when playing the simulation
- EditorUtility.DisplayDialog is not shown when Input.GetMouseButtonDown is called a second time
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