Search Issue Tracker
By Design
Votes
0
Found in
2021.3.5f1
2022.1.3f1
2022.2.0a18
2023.1.0a1
Issue ID
UUM-7579
Regression
No
Intensity parameter ignores Light Layers causing incorrect lightning when additional lights are disabled
Reproduction steps:
1. Open the "MainLightBug_LightLayers" project
2. Open "SampleScene" Scene
3. Observe the Game view
Expected result: Cube is red
Actual result: Cube is black, looks unlit
Reproducible with: 12.1.7 (2021.3.5f1), 13.1.8 (2022.1.8f1), 14.0.3 (2022.2.0a18, 2023.1.0a1)
Could not test with: 10.9.0 (2020.3.36f1) (Light layers not introduced in this version)
Reproduced on: 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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
The cube is not expected to be lit in the given repro project.
URP has the concept of a (global) main light. In the supplied project the blue light has highest intensity and will therefore be the main light.
The cube lives on a rendering layer not affected by that main light and so if light layers are enabled and additional lights (in this case the red light) are disabled, the cube does not receive any lighting.