Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2020.3.X, 2021.1.X
Votes
1
Found in
2020.2
2020.2.2f1
2021.1
2021.2
Issue ID
1310485
Regression
No
Collision.relativeVelocity always return zero when using ArticulationBody on collision
How to reproduce:
1. Open the attached project's "case_1310485-Project.zip" Scene labeled "SampleScene"
2. Enter the Play Mode
3. Inspect the Console Window
Expected result: "Collision.relativeVelocity" values are populated on the initial collision
Actual result: "Collision.relativeVelocity" values are not populated on the initial collision
Reproducible with: 2020.2.4f1, 2021.1.0b6, 2021.2.0a4
Couldn't test with: 2018.4.31f1, 2019.4.20f1 (ArticulationBody Component is not available)
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
- [Quest 2] Surface shader and multi-view sampling custom textures broken in Quest 2
- Lighting Data asset is not created when baking multiple Scenes at the same time
- Performance issues when instantiating a recognizer under UnityEngine.Windows.Speech
- Build fails with "Exception: Unity.IL2CPP.Building.BuilderFailedException: Build failed with 0 successful nodes and 0 failed ones" when building the project for iOS
- [Android] .aab Build fails when using Asset Bundles
Resolution Note (fix version 2021.2):
Fixed in Unity 2021.2.0a11 and above
Resolution Note (fix version 2021.1):
Fixed in Unity 2021.1.2f1
Resolution Note (fix version 2020.3):
Fixed in Unity 2020.3.5f1