Search Issue Tracker
Won't Fix
Votes
2
Found in
2022.2.11f1
Issue ID
UUM-30336
Regression
No
Shadow cast causes graphical artefacts in the Player when cascading is enabled
How to reproduce:
1. Open the project “IN_30654”
2. Press File → Build And Run
3. Observe the shadow on the tent
Expected result: shadows cast without issues
Actual result: shadows cast cause graphical artefacts
Reproducible with: 2022.2.11f1
Couldn't test with: 2020.3.46f1, 2021.3.20f1, 2023.1.0b8, 2023.2.0a6 (due to compiler errors)
Reproducible on: Windows 10 Pro
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
For this case it's not an issue in URP but in the custom shader "Dreamscape_Surface.shader" in the project. The keywords for Main Light Shadows need to be declared together so only one can be selected in each draw call.
Like so:
#pragma multi_compile _ _MAIN_LIGHT_SHADOWS _MAIN_LIGHT_SHADOWS_CASCADE
In that shader _MAIN_LIGHT_SHADOWS and _MAIN_LIGHT_SHADOWS_CASCADE are declared separately so it's possible for both keywords to be enabled at the same time. This made the REQUIRES_VERTEX_SHADOW_COORD_INTERPOLATOR define to be declared and is the reason for the issue happening in this case.