Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
5.3.3p3
Issue ID
843626
Regression
Yes
[5.4][Threading] CullDirectionalShadowCasters performance regression in 5.4+ on lots-of-cores CPUs (e.g. 24 thread Xeons)
Reproduction steps:
1. Open the attached project (Scratch53_MeshSkinningProfiler.zip);
2. Open the scene (Training Room.unity);
3. Enter the play mode;
4. Open the profiler window;
5. Observe CameraRender>Culling ms.
Expected result: The project's performance is normal, no spikes in the CPU Usage.
Actual result: The project is running very slow.
Reproduced on: 5.4.1f1 and newer versions.
Not reproduced on: 5.3.3p3 version of Unity.
Note: This regression is very hardware specific. The bug appears only on Intel(R) Xeon(R) CPU X5680 with 24 cores.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment