Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.1.X, 2020.2.X
Votes
0
Found in
2017.4
2018.4.8f1
2020.1
Issue ID
1181701
Regression
No
Cloth simulation is not natural when Time Scale is changed from one that's close to zero to 1
Steps to reproduce:
1. Open user's attached project
2. Open Project Settings window
3. Go to Time settings
4. Enter Playmode
5. Change Time Scale to 0.001 and then back to 1
Actual result: when Time Scale is changed from 0.001 to 1, Cloth moves way more than it should on such Time Scale
Expected result: when Time Scale is changed from 0.001 to 1, Cloth moves at the normal speed
Reproducible with: 2017.4.35f1, 2018.4.14f1, 2019.2.16f, 2019.3.0f3, 2020.1.0a16
Comments (2)
-
SonicBloomEric
Oct 26, 2020 21:23
(As an addendum to my last comment, I should note that the impulses resulting from the collision are far more muted after updating to 2019.4.13f1...)
-
SonicBloomEric
Oct 26, 2020 21:22
I believe we were seeing this with collisions involving Physics.SphereCast (and brethren) as well.
The annoying thing is that the Physics interactions shouldn't have happened in the first place due to layer mask settings. It seems layer mask settings may be ignored by the Physics.*Cast APIs with very low time scales (and thus fixed time step values).
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
- 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
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.0a1
Resolution Note (fix version 2020.2):
Fixed with: 2020.2.0b8
Resolution Note (fix version 2020.1):
Fixed in 2020.1.11f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.13f1