Search Issue Tracker
Fixed in URP 12
Votes
2
Found in [Package]
12.0.0
Issue ID
1304614
Regression
No
[URP] Shadows have multiple artifacts
Reproduction steps:
1. Open the attached "case_1304614.zip" project
2. In the Project window, select Settings/UniversalRP-HighQuality asset
3. In the Inspector, change the Shadows/Split 1 value from 0 to 1
4. Observe the Scene and Game views
Expected result: Shadow is rendered properly
Actual result: Shadow has artifacts, it looks like a cut off sphere
Reproducible with: 7.5.3 (2019.4.20f1), 10.3.1 (2020.2.3f1), 11.0.0 (2021.1.0b5), 12.0.0 (2021.2.0a4)
Could not test with: 2018.4.31f1 (URP is not supported)
Note:
1. The issue is reproducible only with the certain Cascade Split values
2. The artifacts mostly have a shape of a sphere
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
SilverStorm
May 07, 2021 21:41
Update this issue has now been resolved finally thanks to the Unity Bug Support Team the answer lies in your light settings Near Plane value which defaults to 0.1simply change it to 1 and problem solved! The Near Plane of your Light handles this clipping. Happy Days!
SilverStorm
Mar 04, 2021 05:53
It's been two months and many updates without a "Fix In Review" message. I thought all bugs get fixed as soon as they are reported but I guess not, gotta say this lowers the incentive to even bother reporting future bugs at all. Quite a toxic relationship with this engine.
SilverStorm
Feb 12, 2021 03:02
A kind of workaround is to set the split very low near zero but the quality of the shadows goes down significantly so definitely need a fix.
SilverStorm
Feb 12, 2021 02:58
I'd like this fixed asap. Glad to know it will tell me which Unity update will fix it. Pointless to update until it's fixed. Is there a workaround until then?