Search Issue Tracker
By Design
Votes
0
Found in
4.1.2f1
Issue ID
540645
Regression
No
[Deferred] Light culling mask is not respected when using deferred rendering
Steps to reproduce :
- import the project attached
- open the scene
- change to forward and vertex lit rendering and notice the cube
- change to deferred rendering and notice the cube is lit
Comments (1)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Psycho-Designs
Apr 19, 2017 15:35
Just a heads up for those who find their way here through google. When using deferred rendering, you can only exclude 4 layers from lights across the whole game. So if you have 10 layers, and you set a light to just affect one layer, you're excluding 9 layers and that can cause issues like lights not respecting culling masks. Forward rendering doesn't have this issue