So I’m working on this Idle To Run animation, and there’s about 8 frames at the beginning where the character isn’t actually moving forward. He leans forward first, then starts moving about 8 frames later. But when I put it in-engine, the character starts moving as soon as I push Forward.The animation doesn’t match, which results in it looking like the character is sliding. What I would like to have happen is when I push forward, the animation starts (the character starts to lean forward) and then 0.3 seconds or whatever later, the character actually starts moving, to match the animation. How can this be accomplished?
The cheap way. Disable movement but make sure the button press is being sent to the anim bp (as a bool provably).
then use an Anim Notify to enable the movement after the 8 frames…
Anim notifies are accurate if you use it as branching point in an anim montage. You may want to make an anim montage where it starts the run, and loops the parts where it’s actually running. Or you could set up a state machine where it goes into the run, and once it transitions out of the begin run state and into the looping run state, enable movement.
Hmmm… I’m not sure if I understand what you meant, but it did give me an idea. Could I use root motion on the begin run animation to get the speed I want?
I disagree on this. It’s a bad idea to hook a montage or root motion into it.
gamepad axis already give you fractal axis compared to a keyboard.
meaning they slow down.
How about you just cheat it in code.
Instead of allowing the input to go from 0 to 1 on its own, pass it through a lerp.
First ceil to obviate gamepads.
Then place in a branch. Use the axis being > 0 AND a boolean.
on false set the boolean to true.
the true branch will now have cycled once through the false, and subsequently passed to the true.
Place a timeline play from start, make the timelime something like .3sec, with a value going from. 0 to 1 and you can also use a curve.
pass that value unto a movement input on play.
toggle a sexond boolean when it completes.
Add another branch to check for the new bool. This will be triggered and allow for the user input to be direct after the timeline.
that should give you the effect of acceleration you want - regardless of what controller gets used.
Don’t forget that the first and second bool have to be reset then if the input is released in order to do it again.
It’s complementary. The capsule keeps moving at whatever rate the input imparts unless you use root motion or override the root with an animation curve.
simply adding a stare won’t cause the character not to slide during that state of a direction is pressed…
