Search Issue Tracker
By Design
Votes
0
Found in
2022.3.62f1
6000.0.50f1
6000.1.4f1
6000.2.0b3
Issue ID
UUM-107669
Regression
No
Shadows are cast with artifacts on GameObjects when the light type is set to Point
How to reproduce:
1. Open the attached “IN-102650” project
2. Open the “First Level” scene
3. Observe the shadows on the “PlayerRocket” and “Cube (1)” GameObjects in the Scene view
Expected result: Shadows render smoothly
Actual result: Shadows render with lines or ridges
Reproducible with: 2022.1.0a1, 2022.3.62f1, 6000.0.50f1, 6000.1.4f1, 6000.2.0b3
Reproduced on: Windows 11, macOS12 (M1), macOS15 (M4) (user reported)
Not reproduced on: No other environment tested
Notes:
- Disabling or changing the light type to the “Point Light (weird shadow)” GameObjects makes the issue disappear
- Issue appears slightly differently on Windows and Mac
- Adjusting the bias helps the issue with the shadows on the Rocket and Cube but smaller ridged shadows can still be seen on other objects
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
When using shadow maps, the resulting shadows often have aliasing issues that result in artifacts. You can reduce these artifacts by increasing the shadow map resolution and/or by using soft shadows and/or by adjusting your scene to not expose the aliasing.
So as far as I can see in the attached project, this is the expected behavior, but if I missed something please feel free to re-open the bug and let us know.