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
- With specific Windows 10 settings, the player window resolution does not match the values passed into Screen.SetResolution()
- Material leaks memory when using PostProcess-Layer
- [URP] Adreno GPU is not getting the required vertex data
- [DX12] ShaderData.VariantCompileInfo.ShaderData contains 38 extra bytes on DirectX 12
- Dynamic lights still show up in the Profiler consuming time when "Main Light" and "Additional Lights" are disabled in the UniversalRP-HighQuality asset
Add comment