Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.2.20f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1112631
Regression
No
Cubes not drawn to shadow map when their Y scale is 0.14 and directional light is almost perpendicular to the XZ plane
How to reproduce:
1. Open attached project "case_1112631-ShadowIssue" and scene "SampleScene"
2. Inspect the Scene or Game View
Expected result: both "Cube (1)" and "Cube (2)" cast hard shadows on to the "Cube" GameObject
Actual result: the "Cube (1)" and "Cube (2)" GameObjects don't cast shadows
Reproducible with: 2017.4.20f2, 2018.3.6f1, 2019.1.0b3, 2019.2.0a5
Note: the above cubes don't cast shadows when the Y scale is set to exactly 0.14 and the directional light has a rotation of 90.00001 around the X-axis. Inspecting the frame debugger instruction for this mesh shows that nothing is drawn to the shadow map, even though the call is there. Also, this problem is present for any number of such cubes, not just two.
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
- [Linux] UI picking is offset to the left when Reference DPI and Fallback DPI differ
- Scrolling in a default ScrollView in WebGL builds is slower when compared to other platform builds and the Editor
- Physics 2D Manager documentation page is missing
- Duplicate External Textures start appearing when a Texture created with "CreateExternalTexture" is modified causing Memory Usage spikes on VisionOS
- Silent crash when using a "Blend Shape" in a "Skinned Mesh Renderer" to move vertices to Vector3.positiveInfinity, and "Occlusion Culling" is baked
Resolution Note (2019.3.X):
As we are not focusing on the built-in render pipeline we are aiming to close this bug. As a workaround we suggest to aggressively adjust the near/far plane, and normal bias for shadows. Or alternatively move to LWRP (for mobile) or HDRP (desktop/console), where this issue does not reproduce