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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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