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
- Desktop Linux runtime does not respect -popupwindow command line argument
- Shader Graph more options dropdown button does not open the dropdown when clicked all the way to the right of the button
- “Attempting to draw with missing bindings“ warning lacks root cause indication and is thrown each frame when StructuredBuffer is accessed on DirectX12
- Shader Graph Import Settings documentation leads to "Sorry... that page seems to be missing!" page when opened through the documentation button in the Inspector window
- Unexpected Material change/transparency when switching between ShaderGraph and material at runtime in HDRP
Add comment