Search Issue Tracker
Won't Fix
Votes
0
Found in
5.0.0a12
Issue ID
613498
Regression
Yes
Switching Time.timescale value between a very low number and 1f causes Cloth component to behave non-physically
Steps to reproduce:
1. Create a project which makes use of Cloth component.
2. Create a script which controls Time.timeScale accordingly. Make sure Time.timeScale is set to 0.00001f at start.
3. Enter play mode. Cloth will be not moving
4. Set Time.timeScale to 1f cloth starts to fall.
5. Set Time.timeScale to 0.00001f again - cloth should stop as if it was step 3, however it is still moving.
6. Set Time.timeScale to 1f again - cloth moves unexpectedly fast.
This is not going to be fixed as Unity 5 will have a new Cloth component.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment