Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.2.X, 2019.3.X
Votes
0
Found in
2019.2.7f2
2019.2.8f1
2019.3.0a1
2020.1.0a1
Issue ID
1189951
Regression
Yes
GameObject with SpringJoint2D component isn't affected by RigidBody2D Mass when Freeze Position X is checked
How to reproduce:
1. Open the attached project ("case_1189951-Project.zip")
2. Open the SampleScene in the Scenes folder
3. Enter the Play Mode
Expected result: The platform sinks by colliding with RigidBody2D which has Mass.
Actual result: The platform doesn't move.
Reproduced in: 2019.2.7f2, 2019.2.9f1, 2019.3.0b6, 2020.1.0a8
Not reproduced in: 2017.4.33f1, 2018.4.11f1, 2019.2.7f1
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
- GitHub and GitLab "Personal Access Token" is periodically cleared while Unity Hub is running on Linux
- Attribute on Toolbar Overlay does not resolve when importing .unitypackage
- Remote repository size is not shown for GitHub repositories when expanding project details
- "Repository name" field and "slug preview" don't have correct validation and become inconsistent when unsupported characters are entered
- Package Manager throws ScriptableSingleton related errors after a package was installed while there were pending package manifest changes
Resolution Note (fix version 2020.1):
This issue has nothing whatsoever to do with the SpringJoint2D or any joint related functionality. It's an issue caused by the XY constraints where it incorrectly calculates the scaled contact mass. In short this means that in the case project the contact causes the wrong forces to be calculated.
Fixed in: 2020.1.0a11, 2019.3.0b9, 2019.2.11f1