Child Nodes with Physics not Moving with Parent node

[PJamaLabs]

As title says. I have also found these topics about same issues in C++ version from years ago.

The problem I am having is if the Nodes with physics attached are stationary they they do not move. Any with movement which I am updating in Update then these move with the parent node.

Parent-Child Physics body position in Cocos 3.4

Hi guys, i updated Cocos lib to 3.4 from 3.3, and i have problem… I am creating sprite, setting physics body to it, and adding sprite to parent node. Then i am moving the parent node (change pos to -X) and the physics body (child and also child sprite itself) stays fixed on the screen as it would be not related to sprite, or to anything! In 3.3, if i moved the parent node, its child Sprite moved, and Sprite’s physics body too… What’s wrong? How should i manage it? Here is sample code: a…

Issue in the relation between physics and node hierarchy

Hi, after many tests I’m almost sure there is a bug in the way physics and node hierarchy interact. In fact, when you create a node that contains physics bodies, if you move the node the sprites move with the node, but the physics bodies don’t. Please correct me if i’m wrong, thank you

[PJamaLabs]

I have found a way around it but its not ideal at all. On the nodes update I check if position is different from its start position. If its the same I chance x position by 0.001 and set a flag for forcedmove. then on next update I check forced move and if set I set position back to start position. etc etc

[phero_constructs]

Not sure this is 100% an issue with CC since I could imaging that children with rigid bodies need to attached to their parent in Box2D as well as in CCs hierarchy. So maybe it’s by design?

But I would also like to find a correct way of doing it since our next game could be dependant on this feature.

[mirrorlink]

@PJamaLabs hey have you found any better way around this issue? I am experiencing the very same problem. Thanks