Thanks for that info, I’m gonna try this out. I’ve actually tried using the Result before, and I found that sometimes the result was WillNotReach at random - my guess was because it was too small a unit/number or something like that. In these cases I tried to do a final TeleportTo after MoveTo, which helped a different type of jerkiness. So that, in combination with what you suggested, is what I’m going to look into right now. Thanks!
EDIT: It may have helped in my situation, but didn’t completely eliminate it. But now that I’m back fiddling with it, I noticed that the “ghosting” is actually ahead of my movement - like for one frame it is actually teleporting to the destination first, then frame after it start the actual MoveTo from it’s existing location…
…so I managed to fix the “ghost teleport frame” completely by telling my prop to TeleportTo its current position before every MoveTo command. But with a MoveTo speed of 0.1, and the fact that I’m sending it position updates every tick, still results in general performance issues. Choppy, but at least it’s not doing the ghost teleport frame thing now.
Again, this doesn’t happen if I set my MoveTo speed to > 0.34 (longer than 1 tick) - the performance is perfect.
So maybe we’re just asking too much of Verse? That is, assuming the OP is doing the same thing as me - recursive/repeated/looped MoveTo commands that are shorter than a tick.
I think what might be happening in my case is that I’m re-using vector3’s based on the props original location instead of copying the values. Either that or Verse itself has a problem with “not getting the actual latest variables”.
Or maybe I should be changing my code to have a or effect on a method somewhere, and that’s why the vector3’s seem to be “messing up sometimes”. I admit I don’t know how/when/why to use these two effects in practice.
I’ve spent a lot of time on this haha, now that it’s out in the open on the forums I’m keen to hear any input and share my own findings.
EDIT2: Turns out the pre-teleport didn’t solve it, after all, it just made it even less likely. Hmmm.