Search Issue Tracker
Fixed
Fixed in 2021.3.X, 2022.1.X
Votes
0
Found in
Issue ID
1424996
Regression
No
[HDRP] Incorrectly allocated slots for Screen Space Shadows
Version tested: 2022.2.0a12
Steps to reproduce:
1) Open attached project, VFXShadowsTest scene
2) In HDRP set Max Screen Space Shadows to 4
3) Observe that the scene has 4 lights: dir (1 slot), point (1 slot), spot (1 slot), area (2 slots)
4) in Rendering Debugger/Light enable ScreenSpaceShadows debug mode
5) Scrub Screen Space Shadow Index and observe that the same dir light shadow is bound to indices 0 and 1
Bonus to this bug
We have 4 lights (5 slots) but area light shadows start looking correctly only when we allocate 6 shadow slots in settings. As Anis has explained memory slots are allocated in chunks of 4 and area light inefficiently allocates itself in the second chunk (because it can't span over two memory chunks, from slot 4 to 5).
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
Add comment