Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.2.X
Votes
0
Found in
2019.3.0f3
2019.3.14f1
2020.1.0a16
2020.2
Issue ID
1250914
Regression
Yes
GetShadowCasterBounds method returns true when all shadow casters are outside of the shadow distance
How to reproduce:
1. Open the attached '04 Directional Shadows.zip' project
2. Open 'SampleScene' Scene
3. Zoom out the Scene View
Expected result: 'not rendering shadow map' messages are logged to the Console
Actual result: No logs are printed in the Console, thus shadow maps are always in use
Reproducible with: 2019.3.0f3, 2019.4.7f1, 2020.1.0a16, 2020.1.2f1, 2020.2.0a20
Not reproducible with: 2019.3.0f2, 2020.1.0a15
Could not test with 2018.4.26f1 (due to errors thrown in the Console)
Notes:
- Selecting an object causes Console logs, don't have anything selected
- When zooming scene in enough, messages are logged to the Console
- Reproducible with Metal, Open GL, DX11, DX12, Vulkan
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a1. Shadow culling planes were being incorrectly set using the camera's far clipping plane distance, this will now be fixed to correctly use the shadow distance setting.
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0b5