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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment