Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
1
Found in
2019.4.40f1
2020.3.35f1
2021.3.6f1
2022.1.8f1
2022.2.0a18
2023.1.0a1
2023.2.0a1
Issue ID
UUM-8474
Regression
No
Shadow Cascades are acting weird and are rendered differently when changing the View Position
How to reproduce:
1. Open the attached project "ShadowCascadesIssue_3D"
2. Observe the Scene View by changing the View Position
Expected result: Shadow is displayed correctly and is rendered the same way not depending on the View Position
Actual result: Shadow is changing with the View Position; the more you zoom, the more parts of the shadow are missing
Reproducible in: 2019.4.38f1, 2020.3.36f1, 2021.3.5f1, 2022.1.5f1, 2022.2.0a18, 2023.1.0a1
Reproducible on: Windows 11 Pro
Note: The issue is reproducible in the 3D Project, but is also reproducible in the URP project. The behavior is different but the shadows are still changing depending on the View Position. The attached project "ShadowCascadesIssue_URP" shows this behavior.
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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (2023.2.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.