Search Issue Tracker
By Design
Votes
0
Found in
6000.0.28f1
6000.1.0a5
Issue ID
UUM-87943
Regression
No
CullingResults.GetShadowCasterBounds Results Remain Unchanged Despite Restricting Affected Objects with Rendering Layers
Reproduction steps:
1. Open the attached “LightRenderingLayerMaskBug.zip“ project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Enter the Play Mode
4. Observe the bounds of “Default Light“ and “LightLayer1 Light“ in the Console
Expected result: “Default Light” bounds are “Center: (0.00, 0.41, 0.00), Extents: (5.00, 0.50, 5.00)“, “LightLayer1 Light“ bounds are “Center: (-3.00, 1.00, 0.00), Extents: (0.50, 1.00, 0.50)”
Actual result: Both light bounds are “Center: (0.00, 0.96, 0.00), Extents: (5.00, 1.05, 5.00)“
Reproducible with: 6000.0.28f1, 6000.1.0a5
Couldn’t test with: 2021.3.45f1, 2022.3.52f1 (Missing features with older Core RP versions)
Reproducible on: M1 Max MacOS 14.6.1
Not reproducible on: No other environment tested
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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
Resolution Note:
RenderingLayers are used to filter out objects from culling results. As such, they are not applied to CullingResult objects, but later on when creating RendererLists with one of ScriptableRenderContext.CreateRendererList, ScriptableRenderContext.CreateShadowRendererList or ScriptableRenderContext.CreateSkyboxRendererList methods.