Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2020.3.X
Votes
0
Found in
2018.2.7f1
2020.1
Issue ID
1296194
Regression
No
Changing parent of teleported game object with ArticulationBody component blows up simulation
Create a “complex” articulation body hierarchy.
Call articulationBody.Teleport() on the root of the articulation body hierarchy
Immediately after set the transform parent of the root articulationBody to a new transform.
Observe physics explosion and NANs in the transform components position / rotation in the articulation hierarchy.
It should just continue behaving normally like it is without changing parent transform after teleport.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment