Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4
2019.4.25f1
2020.3
2021.1
2021.2
Issue ID
1333564
Regression
Yes
Cloth constraint values change when upgrading from Unity 2018.4 to Unity 2019.4
Steps to reproduce:
1. Download and open the project "ClothConstraintBug.zip" in Unity 2018.4.34f1
2. Open Assets/Scenes/SampleScene.unity
3. Select the GameObject "Cape_Botton_Mesh" under the parent GameObject "Char_Thor_Cape_Mesh_PREFAB"
4. In the Inspector, click on the "Edit cloth constraints" button under the Cloth component (top left button)
5. Notice the value of the Cloth constraint points (Max Distance is 0 at the top and gradually increases to 0.5 at the bottom)
6. Open the same project in Unity version 2019.4
7. Repeat steps 2 to 5
Expected result: The value of the Cloth constraint points remain unchanged
Actual result: The value of the Cloth constraint points have been shuffled
Reproducible with: 2019.4.26f1, 2020.3.7f1, 2021.1.6f1, 2021.2.0a16
Not reproducible with: 2018.4.34f1
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (2019.4.X):
This issue is not caused by cloth but instead the mesh import settings being set by default to change vertex order(this behavior was not present in 18.4), changing the import settings to not reorder vertices will fix this issue. Currently there's no plan for actually modifying 18.4 to store vertex to index mapping in order to avoid this.