Search Issue Tracker
By Design
Votes
3
Found in
2019.4
2019.4.0f1
2020.3
2021.1
2021.2
Issue ID
1321480
Regression
No
Occlusion culling not working on Shadow casters when Shadows are behind a Static Object
Reproduction steps:
1. Open user attached Project
2. Open Assets\Scenes\SampleScene
3. Press Play
4. Enable the Stats
Expected result: Occlusion Culling reduces the Tris number to 50-150
Actual result: The Tris number is still 3.7M
Reproducible with: 2019.4.24f1, 2020.3.2f1, 2021.1.1f1, 2021.2.0a11
Could not test with: 2018.4 (Project breaks)
Notes:
It's possible to adjust occlusion settings where most Tris are Culled, but the Occlusion should be functional without min-maxing the settings for every situation (See the attached Overview for more details and a more streamlined Project)
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
- Crash on memcpy when opening a project that loads TSS files
- Multiple errors appear when compiling a ShaderGraph shader's code in a specific project
- TextMeshPro memory leak occurs when reloading the scene using Addressables
- Vector3 node has no X, Y, Z outputs when adding Vector3 node in the Visual Effect Graph
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
Resolution Note:
The occluder (the top cube) is 5000 x 5000 units wide and 1 unit tall. The "Smallest Occluder" setting in the culling data bake is 20 units. This is clearly wrong, since the smallest occluder is 1 unit. Umbra just misses the occluder, and hence renders a bunch of extra geometry.
Here's a few ways to work around this:
1. Reduce the size of your scene.
2. Increase the thickness of your occluder.
3. Reduce the "Smallest Occluder" parameter value to 1. This will take an immense amount of computation and data, so use an OcclusionArea to tightly fit the area of interest that you want the occlusion data to be baked in.