Search Issue Tracker
Fixed in 14
Votes
0
Found in [Package]
10.1.0
Issue ID
1418462
Regression
Yes
[URP] Shadows are rendered for the first cascade only when using GLES2
How to reproduce:
1. Open project "TestShadowsClippedGLES2.zip"
2. Make sure GLES2 is selected in Player settings
3. Build and Run on Android
4. Observe the Scene
Expected result: All objects in Scene have shadow
Actual result: Only the first object has a shadow
Reproducible with: 10.1.0 (2021.1.0a1), 10.8.1 (2020.3.33f1)
Not reproducible with: 7.7.1 (2019.4.38f1), 8.1.0, 10.0.0-preview.2 (2021.1.0a1)
Could not test with: 12.1.6 (2021.3.1f1), 13.1.7 (2022.1.0b16) (URP build errors related to GLES2), 14.0.2 (2022.2.0a12) (built Scene is completely broken with GLES2)
Note:
- GLES2 is deprecated on versions that could not be tested
- Does not reproduce with GLES3 or 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
- 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
Resolution Note (fix version 14):
Fixed in: 2022.2.0a15
We cannot enable cascades on GLES2 since we do not support them for a while.
An info box was added explaining this behaviour when targeting GLES2 in Editor, so users are informed about the cascades falling back to 1
The max distance setting should also work correctly now when a single cascade is used