Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.59f1
6000.2.6f1
6000.3.0b3
6000.4.0a1
6000.5.0a1
Issue ID
UUM-121659
Regression
No
Shadows are broken in ECS Graphics when using deeply nested object hierarchies
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Scenes/Sandbox.unity“ Scene
3. Enter the Play Mode
4. Click the "animals" button in the bottom-right corner in the Game view
5. Click anywhere in the Game view to spawn animals
6. Observe the shadows in the Game view
Expected result: Shadows should render correctly on all spawned animals without flickering or covering the entire scene
Actual result: Shadows flicker in and out intermittently or cover the whole scene
Reproducible with: 6000.0.59f1, 6000.2.6f1, 6000.3.0b3, 6000.4.0a1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
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
- Invalid Clip Method
- WebGPU error with Fantasy Kingdom and GPU Resident Drawer
- WebGPU fails with height fog in Fantasy Kingdom
- Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
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 (6000.5.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.