Question by kodishfish · Oct 09, 2022 at 11:07 PM · rigidbody2d parent-child transform.translate

can i use translate on parent of an object with rigidbody?

ok so. in my game i have a "player" empty game object. "player" has a c$$anonymous$$ld called "sprite", just for animating, and another c$$anonymous$$ld called "shadow", because the player's shadow is relevant in t$$anonymous$$s game. "shadow" has a rigidbody2d because i need to use OnCollisionEnter to check if it's touc$$anonymous$$ng some other gameobjects.
i need the player to be able to move themselves by controlling the parent object. i know that you shouldn't use transform.Translate() on an object with a rigidbody, so is it okay to use Translate to move the parent of a c$$anonymous$$ld with a rigidbody? t$$anonymous$$s is a 2d game, so i don't really want to add a rigidbody to the parent and have to deal with forces and mass and drag and everyt$$anonymous$$ng.

1 Show 1

SurreyMuso · Oct 10, 2022 at 08:57 AM 0

I'm voting up this question because it's a really good one. Very interesting use case...

It strikes me that the "player" is actually your shadow and the sprite is just a visual artefact of your player and so the sprite should be a child of the shadow. Might that help? It would mean putting your script on the shadow, not the empty game object and moving the shadow using RigidBody.MovePositon but that shouldn't be a hardship. Set Gravity Scale, Drag and Angular Drag to 0.

Then again, can the sprite pass through walls and other game objects? You would need physics as well to prevent it doing so. In any case, if you have a composite game object with multiple rigid bodies, you may need to use joints to keep them together. I know that adds another layer of complexity but, unless you have a single game object comprising body and shadow together with a polygon collider you risk shadow and sprite separating.

Still thinking about this one. First time I've come across this idea. Nice one...