Search Issue Tracker

Active

Under Consideration for 2022.3.X, 6000.0.X, 6000.1.X, 6000.2.X, 6000.3.X

Votes

0

Found in

2022.3.61f1

6000.0.48f1

6000.1.1f1

6000.2.0a10

6000.3.0a1

Issue ID

UUM-104524

Regression

No

2D Colliders, attached to a grandchild GameObject, aren't immediately destroyed when destroying the parent GameObjects in FixedUpdate

-

How to reproduce:
1. Open the attached “IN-99890_Physics2DBug” project
2. Open the “TestScene“
3. Enter Play mode
4. Observe the “Red Sphere“ and “Blue Sphere“ GameObjects in the Game view

Expected result: Both spheres fall at the same time without colliding with anything until they touch the ground
Actual result: The “Red Sphere“ GameObject collides with the destroyed “Red Cube Root“ GameObject and reaches the ground later than the “Blue Sphere“ GameObject

Reproducible with: 2022.1.0a10, 2022.3.61f1, 6000.0.48f1, 6000.1.1f1, 6000.2.0a10

Reproducible on: MacOS 15.3 (M4), Windows 10 (by user)
Not reproducible on: No other environments tested

Notes:
- Reproducible in Standalone Player
- The “Red Cube Root” GameObject has the BoxCollider2D component attached to a grandchild GameObject, while the "Blue Cube Root" GameObject has the BoxCollider2D component attached to a direct child GameObject
- The "TestScript.cs" script, attached to both spheres, changes their Rigidbody velocity downward, then destroys the “Red Cube Root“ and “Blue Cube Root“ GameObjects
- The discussion thread regarding this issue: [https://discussions.unity.com/t/destroyed-2d-collider-not-removed-immediately-from-physics-if-grandchild/1634303/3|https://discussions.unity.com/t/destroyed-2d-collider-not-removed-immediately-from-physics-if-grandchild/1634303/3|smart-link]

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.