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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
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.