MoveTo is severely Buggy [Fixed Fortnite v25.0]

Development Programming & Scripting Verse
, , ,
39

It seems that MoveTo() acts way worse than before for my use case.
I’m trying to move a prop on every tick so it follows the player.

Before (v24, video starts at 0:30)

After (v25)

I’m a bit sad because the “fix” was retroactive (thus applied to published islands), and the island that used this script was featured in Discover yesterday…

Here’s the code:

loop:
    Prop.MoveTo(Character.GetTransform().Translation, Character.GetTransform().Rotation, 1.0/30.0) # one tick (when server is not laggy)

I tried so so so so so so so many different ways, but none could work, it was back in v24 though.

For those who used the same script as me, the best way I came up with was to reduce the movement TickRate to 0.1. (a better refresh rate will introduce ghosting and teleports)

Also as I tried to fix my script really quick, I noticed a few things :

  • Verse script only execute on server ticks, but MoveTo’s duration is free to set (it only has to be above one tick), meaning that you cannot perfectly match your duration with your calls. (just a thought, maybe I’m wrong)
  • The animation controller MovementCompleteEvent doesn’t fire at the same time than its StateChangedEvent (when the new state is set to Stopped). AnimationComplete seem to be fired one frame after state is Stopped. Which one to believe ?
  • I’m still sad
2 Likes