Search Issue Tracker
Duplicate
Votes
28
Found in
Issue ID
1058733
Regression
No
[LWRP] Directional Light Culling Masks don't work properly
SRP Repo: Issue #1019
In LWRP: If you make a scene with objects set to two different layers and then make two directional lights set to affect those layers separately, the directional lights will still affect both layers.
-
Irwin12221
Apr 04, 2024 10:00
sd
-
albertobelluci
Mar 29, 2024 07:18
Thank you
-
denisbrown0306
Nov 28, 2023 16:44
-
kimokarim
Jul 24, 2023 12:35
-
hw-unity
Jul 20, 2023 06:43
the other version?
-
david16s
Jul 12, 2023 08:17
If the directional light culling masks are not functioning correctly in a LWRP (Lightweight Render Pipeline) setup, there could be a few potential causes.
Double-check the culling mask settings: Ensure that the culling masks for the directional light are correctly assigned to the relevant layers and that the layers are properly configured in the scene.
-
david16s
Jul 12, 2023 08:16
If the directional light culling masks are not functioning correctly in a LWRP (Lightweight Render Pipeline) setup, there could be a few potential causes.
Double-check the culling mask settings: Ensure that the culling masks for the directional light are correctly assigned to the relevant layers and that the layers are properly configured in the scene
-
david16s
Jul 12, 2023 08:15
If the directional light culling masks are not functioning correctly in a LWRP (Lightweight Render Pipeline) setup, there could be a few potential causes.
Double-check the culling mask settings: Ensure that the culling masks for the directional light are correctly assigned to the relevant layers and that the layers are properly configured in the scene.
-
alisha965
May 20, 2023 07:09
-
cleosizara
Dec 22, 2022 10:00
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #1058836