Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
1
Found in
2020.3.45f1
2021.3.19f1
2022.2.8f1
2023.1.0b6
2023.2.0a4
2023.3.0a3
Issue ID
UUM-29536
Regression
No
Articulation Body steals Colliders from a Rigidbody when the Rigidbody is a child of the Articulation Body
Reproduction steps:
1. Open user attached project "IN-23249_SetMaxImpulseTest.zip"
2. Open Assets > SampleScene
3. Enter Play mode
Expected result: Console window prints that the Collider is attached to the Rigidbody since it's on the same GameObject
Actual result: Console window prints that the Collider is attached to the Articulation Body
Reproduced with: 2020.3.45f1, 2021.3.19f1, 2022.2.8f1, 2023.1.0b6, 2023.2.0a4
Reproducible on: macOS 12.4 (Intel), Windows 10 (by the reporter)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Build fails when building a project containing an 18+ dimension array with IL2CPP
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
Resolution Note:
Closing this issue, with the note that it is fixed in 2023.3 due to a major rework inside the physics tech stack. We do not plan to backport this rework as the workflow of Rigidbody components as children of ArticulationBody components is not a workflow we really support.
Resolution Note (2023.3.X):
Closing this issue, with the note that it is fixed in 2023.3 due to a major rework inside the physics tech stack. We do not plan to backport this rework as the workflow of Rigidbody components as children of ArticulationBody components is not a workflow we really support.