Skeleton stops updating after physicsbones stop moving

oulibha

Hello everyone! I'm aiming to make a creature model that moves kind of like a fish. The two tail bones are simulated physics bones. After running physical_bones_start_simulation() the model looks fine as long as it is kept in motion. As soon as it stops, the skeleton stops updating. (it doesn't even return its skeleton_updated() signal). The two rectangles in the gif track the position of tail PhysicsBones. As you can see, they stay in place as soon as the skeleton stops updating. When the physics simulation is restarted manually it starts working again, but the bones are returned to their original position and the transform looks rigid.

Is this a bug or a feature of the physical bones simulation? If so, is there a way of disabling it?

TwistedTwigleg

Welcome to the forums @oulibha!

I think it is probably a bug. I would suggest making an issue on GitHub for this issue, if there is not one already.

What is probably happening is that the PhysicsBone node doesn't clear the global_pose_override when it is stopped, which causes the bones to always take the overridden position. If this is the case, you can work around the issue by calling set_global_pose_override(bone_id, Transform(), 0.0, false) on each bone affected by physics, which should clear the physics override.