Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.43f1
2021.3.16f1
2022.2.2f1
2023.1.0a24
Issue ID
UUM-25713
Regression
No
Shadows are stuck at max length when changing the Max Length parameter
Reproduction steps:
1. Open the attached “Test Project”
2. Enter Play Mode
3. Select “Universal Reder Pipeline Asset” in the Project window
4. In the “Shadows” section change the “Max Distance” value
5. Observe “Sprite-StartingTileSet_0” GameObject’s rendered shadow
Expected result: “Sprite-StartingTileSet_0” GameObject’s” shadow length changes according to the “Max Distance” value
Actual result: “Sprite-StartingTileSet_0” GameObject’s shadow length doesn’t change
Reproducible with: 10.10.1 (2020.3.43f1), 12.1.8 (2021.3.16f1), 4.0.4 (2022.2.2f1), 15.0.2 (2023.1.0a24)
Reproducible on: Windows 10
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
This is a bad UX/UI issue related to the fact that the Universal Renderer Asset is showing options unrelated to the 2D Renderer (this asset is required for both the 3D and 2D renderer).
While some of the shadow options clearly don't make sense in the context of 2D such as Cascade Count. Max Distance does, but it's not supported. Moving out unshared data is something that is being worked on by the URP team.