Any InterpTo node pretty much needs to be called constantly until the actor reaches its destination.
An alternative would be using a Timeline and a Lerp node to interpolate between the initial location and the target location, but you’ll have to additionally calculate for the distance so that the actor would move with the constant velocity.
@Tuerer I remember that I have seen a code to do it without using Tick event or Input Axis here in the forum, but I don’t remember where. This is why I’ve asked.
The question still remains. Why put yourself through this hardship, there’s nothing wrong with tick.
Tick gets a bad reputation all over youtube, because people who don’t know what they’re doing hang rubbish code on it. I really think the node should be unavailable for the first six months using the engine
This is probably not useful for you any more in 2023 but yes, there are lots of ways you could use InterpTo nodes without using tick, there’s just not good reason too.
You could trigger it from any event in blueprint (or in code if you want) but you will still need to provide it with a DeltaTime value regardless or it will do nothing. DeltaTime is just a float value, so you could get it from anywhere. If you want drive the interpolation forward using some game event instead of the clock, you could just try that and see that it works (at least I’m pretty sure it does).
But that’s not what that node is for: it’s for smoothly moving between values on Tick. I understand it’s pretty light-weight too so again, no reason to do otherwise.