Search Issue Tracker
Fixed in 5.5.0
Votes
1
Found in
5.3.1f1
Issue ID
763922
Regression
No
TargetJoint2D added during runtime ignores collision
Steps to reproduce:
1) open attached project
2) play scene 'TestScene'
- the scene has three cubes, bottom right corner shows expected behavior and upper left shows bug
3) press key 'X' (adds TargetJoint2D)
Expected behavior: collides with the cube in middle
Actual: ignores collision
Workaround: collision starts working if the inspector values of the TargetJoint2D are changed
Reproduced: 5.3.0f4, 5.3.1p4, 5.4.0b3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android][Vulcan] "UNITY_DISPLAY_ORIENTATION_PRETRANSFORM" is always 0 when the render pipeline is URP
- Editor loads for a long time when doing an Undo action in a large Shader Graph
- Memory leak when building AssetBundles
- [Asset Bundle] AudioSource output field not staying connected correctly when loaded from Asset Bundle
- [Android] Duolashock4 controller is not detected after disconnecting and reconnecting controller while the Player is running in the background
Add comment