Search Issue Tracker
Fixed
Fixed in 2022.2.4f1, 2023.1.0a26
Votes
2
Found in
2022.2.0b16
2023.1.0a20
Issue ID
UUM-20184
Regression
Yes
Rendering Layers break additional lights
Enabling rendering layers on the Pipeline asset makes additional lights disappear
Steps to repro:
# Open attached project
# Observe that no additional lights are affecting the plane
# Disable rendering layers on the pipeline asset and see the light turning on
# See that the plane and point lights are all on the Default light layer which means the plane should be lit by the point lights
Comments (1)
-
Disastorm
Jan 13, 2023 17:24
Is this also going to fix the light culling mask when not using Render Layers?
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
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
Resolution Note (fix version 2023.1.0a26):
The issue was that light layer data was missing for additional lights. This has now been fixed.
Resolution Note (fix version 2022.2.4f1):
The issue was that light layer data was missing for additional lights. This has now been fixed.