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
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
- Crash on mdb_page_alloc when opening a project that was running while the PC shut down
- macOS Player freeze when using RunInBackground and Command+Tabbing to and from the application
Add comment