Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.33f1
2022.3.18f1
2023.1.21f1
2023.2.5f1
6000.1.0a7
6000.2.0a1
7000.0.0a1
Issue ID
UUM-59785
Regression
No
[Usability][URP] Static Shadow Caster (from hdrp) flag does nothing
*Steps to reproduce*
# Create a new project or import an existing one using Unity 2021.3 LTS or newer
# Add a 3D object to the scene and select it
# Under the Mesh Renderer component, inspect the Static Shadow Caster flag
*Expected behavior*
* Enabling Static Shadow Caster flag allows user to specify which objects will be marked as static in a cached shadow map
*Actual behavior*
* Static Shadow Caster flag does not work in URP, and is only supported in custom SRPs. Cached shadows maps in URP are still not supported at the time of writing
*Notes*
* Observed in 2021.3.33f1 and all newer Unity releases
* Leaving this option exposed sets wrong expectations and can be confusing to our users
* Recommend hiding this option, and only exposing it once cached shadowmap support lands in URP
* For custom SRP users, allow them to access this flag via the API
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
- Brush Size in the Inspector window does not update when the Brush Size in Scene View is changed
- "ArgumentOutOfRangeException" errors are thrown every time a keyboard key is pressed when renaming a component in UI Builder with a symbol and changing the name after label attribute warning
- Values in "Rect Transform" component are only partially updated when changing values in Prefab Mode
- Same Asset Type Focused Inspectors do not repaint when menus are manipulated
- Bool or Trigger Parameters can be selected via right clicking to the right of a Parameter control in the Animator Window
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.