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
- Inspector loses focus or Material doesn't update when using GetModifiedMaterial with a Mask component
- Crash on GfxDeviceClient::AllocateBufferInternal when entering Play mode using Graphics.RenderPrimitives and Graphics.DrawProcedural in the scene
- Import TextMesh Pro window opens when the Text Mesh Pro Essentials and Examples are already imported when creating a new TextMesh Pro GameObject in the Hierarchy with TextMesh Pro settings reset
- Video is not rendered when the VideoPlayer GameObject is disabled and re-enabled after playback starts while using Material Override render mode
- Selection outline is not shown when selecting a high intensity HDR Swatch preset in Color Picker
Add comment