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
- Crash on ResizeScriptingList<ScriptingObjectPtr> when passing an undeclared variable to the results parameter for GameObject.FindGameObjectsWithTag
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
- Frame spike due to many TreeRenderer.TreeUpdated calls when repositioning terrains in large Scenes
- Crash on GameObject::RemoveComponentFromGameObjectInternal when reparenting Text GameObjects
- [IL2CPP-GarbageCollector] Changing GCMode might permanently disable GC in a multithreaded context
Add comment