Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
14
Found in
2019.2.6f1
2019.2.9f1
2019.3.0b2
2020.1.0a2
Issue ID
1192837
Regression
Yes
Cloth's movement simulation is incorrect when the game object is rotated in world space
How to reproduce:
1. Open the attached 'project-1192837.zip' project
2. Enter Play mode
3. Move the red cloth horizontally forward and backward
3. Move the blue cloth horizontally forward and backward
Expected result: rotated (blue) cloth acts differently from the non-rotated (red) one when being moved horizontally
Actual result: rotated (blue) cloth acts the same way as the non-rotated (red) one when being moved horizontally
Reproducible with: 2019.2.6f1, 2019.2.11f1, 2019.3.0b2, 2019.3.0b9, 2020.1.0a2, 2020.1.0a11
Not reproducible with: 2017.4.33f1, 2018.4.12f1, 2019.2.0a1, 2019.2.5f1, 2019.3.0a1, 2019.3.0b1, 2020.1.0a1
-
Redrag
Feb 21, 2020 14:20
Just tested in 2019.3.2f1. Its still broken. The External Acceleration is still in local space. So I have wasted most of the morning converting my project. Next time I will just do a 5 minute test. Just hang a curtain. Rotate in world space. The wind follows the curtain so it is blowing in local space!
Also, it seems even more buggy than in 2019.2 with constraints vanishing (have to change the layout to bring them back). The model jumps all of the place in the editor. We are going backwards!
-
Redrag
Feb 04, 2020 09:12
Update - I don't think it is using local space either. The direction of the External Acceleration does not seem to relate to the cloth's transform OR world space. It makes me think it is picking up a coordinate system from the mesh.
-
Redrag
Jan 21, 2020 13:34
I have found that the External Acceleration acts locally instead of globally. 2019.2.17f, 2020.1.0a19
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a24
Resolution Note (fix version 2019.3):
Fixed in 2019.3.2f1