Go.set_position lag?

Questions
#1

red_blue_ball_GIF

I have an object1 whose position changes with go.animate. In the update, object1 sets the position of the object2. As a result, the object2 lags behind the object1.

%D0%91%D1%83%D1%84%D0%B5%D1%80%20%D0%BE%D0%B1%D0%BC%D0%B5%D0%BD%D0%B0-1
Буфер обмена-1.png815×267 91.8 KB

3 Likes
#2

I believe go.animate is calculated/updated in the “post update phase” but before rendering but surely someone in Defoldteam can confirm it

1 Like
#3

Defold team, also please explain at what moment physics is updated and sends messages to the game objects? After/before “update phase” or…?

1 Like
#4

The update loop is documented here: https://www.defold.com/manuals/application-lifecycle/#_the_update_loop but it probably needs to be clarified. Physics is updated after scripts if I’m not mistaken @sven?

#5

Yup, that is correct. :+1:

#6

What do you have to say about the subject?
What to do with the lag?

#7

I’d say don’t use go.animate this way. You can use pure Lua tweening library like flux and assign all objects positions at the same time.

#8

You can also use go.set_parent()

1 Like
#9

Did I get it right that this is the order of “update”:

  1. Calling “update” in all scripts
  2. Dispatching messages
  3. Updating physics
  4. Dispatching messages (due to physics)
  5. Updating go.animate animations
1 Like
#10

Almost:

DispatchMessages() is called between the update of each component type.

And the update order for the first types are:

  • script
  • anim
  • gui
  • physics
  • …
7 Likes