[Part 22] Rigidbody2D Movement Not on FixedUpdate

[Sean]

Helpful?

Up

1

::

Hi,

I added Rigidbody2Ds to my enemies to that they’d collide with each other, instead of overlapping, but they started moving incredibly slow.

I realised that the Move() function executes Rigidbody2D movement on an Update, not a FixedUpdate. After I changed it so that the Rigidbody2D movement code was executed through a FixedUpdate, it fixed the issue.

Kind Regards, Sean

• Terence

has upvoted this post.

[Terence]

Helpful?

Up

1

::

Thanks for sharing this Sean. Much appreciated.

1 anonymous person

has upvoted this post.

[Sean]

Helpful?

Up

1

::

Also, regarding the knockback in the Update function, should this be handled by the rigidbody too if one is present?

• Terence

has upvoted this post.

[Terence]

Helpful?

Up

1

::

Yes. Theoretically speaking, putting it on FixedUpdate() should give you more consistent behaviour, so you should always do that when it is possible.

I haven’t run into any issues doing it on Update(), but Unity advises that all changes to Rigidbodies should be made on FixedUpdate() as a best practice.

1 anonymous person

has upvoted this post.

[A_DONUT]

Helpful?

Up

0

::

If u have anymore doubts u can ask here I will be glad to help

[Author]

Posts