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
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
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