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.6.0b5
Issue ID
878604
Regression
Yes
Physics.UpdateCloth in 5.6 takes 3 times longer than in 5.5
Physics.UpdateCloth in 5.6 takes 3 times longer than in 5.5. In 5.5 it takes ~1.5ms and in 5.6 it takes ~4.5ms.
Reproduction steps:
1. Open the project TestCloth - 5.5 on Unity 5.5.2p2.
2. Open the project TestCloth - 5.6 on any Unity 5.6 or 2017
3. Press play in both projects
4. Observe the Physics.UpdateCloth in the profiler of both projects
Expectation: it takes similar amount of time on both versions
What happens: it takes up to 3 times more on the newer version of Unity
Not reproduced on: 5.5.2p2
Reproduced on: 5.6.0a1, 5.6.0b11, 2017.1.0a3
Regression introduced: 5.6.0a1
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
- 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
jaelove
May 02, 2019 10:00
Freaking Insane!
castor76
Dec 17, 2017 05:03
What is mean by postponed? Is it fixed? Or will it be fixed later? For what reason did it get "postponed" ?