Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
1
Found in
2019.2.0a8
2019.3
2019.3.2f1
2020.1
2020.2
Issue ID
1221805
Regression
Yes
Cloth External Acceleration is applied in local space instead of world space
How to reproduce:
1. Open the attached 'project-1221805.zip' project
2. Enter Play mode
3. Observe the movement of both plane's
Expected result: external acceleration is applied in Z-axis (WORLD space) for both planes
Actual result: external acceleration is applied in Z-axis (LOCAL space) for both planes (hence the planes move in the same direction)
Reproducible with: 2019.2.0a8, 2019.2.21f1, 2019.3.4f1, 2020.1.0a25, 2020.2.0a1
Not reproducible with: 2017.4.37f1, 2018.4.18f1, 2019.2.0a6
Could not test with: 2019.2.0a7 (due to a cloth bug in that version)
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
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a21
Resolution Note (fix version 2020.1):
Fixed in 2020.1.3f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.9f1