In engine, direction is part of the vector.
Velocity is the amount of travel defined as per frame you apply to said directional vector.
I guess what you are harping on is that it should be defined as Speed?
But then you won’t be able to pull the correct node from the engine, since there is nothing named Speed other than scalar variables.
Its called Velocity. And its a simple vector that expresses the direction in which the actor moves.
The above was specifically directed to pulling velocity, and extracting the direction of a scpecific axis.
The difficulty of the user is that if you pull forward vector it can tell you X, while Y and Z dont change.
Likewise, when you pull Right vector it tells you changes on Y, but not X or Z.
Hence, making it difficult for him/her to detect direction of travel.
Which is also wholly pointless - just get the direction from the axis input when dealing with controllers.
No point waisting resources on even the most basic calcs when you already know for a fact the input is saying “go left”…
Only, they wanted it that way, and likely I didn’t know better than to tell them not to even try it and stick to the axis 5 years ago.
Ergo, you get the code he kindly shared…
And the follow up info on how to properly set up your blendspaces…