I ran into this issue when upgrading our project from 5.3 to 5.4.
Since I used the node in an actor where I manually set it’s location each tick, I could easily calculate the velocity vector like so:
(this is on tick, before any translation code)
Looks like currently, only the actual physical forces are reported back as velocity (like it says in the name), moving an actor with SetLocation/Transform will result in a (0,0,0) velocity vector as reported (if there aren’t any other forces on the actor, like gravity). I tried all the different physics option but it made no difference. Same with GetVelocity node…
I also used this in animation blueprints a lot, hope there’s a fix soon or at least a replacement for old functionality. If the change is intended, it should be made in a way that does not brake old functionality. (though I’m guessing it’s just a bug)