I think that would not alleviate the problem. I used the Float Tween for a nice smooth acceleration and deceleration, in a fairly elaborate setup (which I now discarded).
The way the Set Velocity action is written, it always seems to hard-overwrite the velocity no matter what. In order to do something like a dash, you need to suspend the Set Velocity, so that the Add Force can work on top of the current velocity (which is maintained, unless changed by the physics).
It's technically correct that when the input is zero, it would also set the velocity to zero. But that can feel weird, because zero can also be interpreted as "no input", rather than "stop movement". I already once encountered the problem with physics objects (see
here also with samples), hence I made a version with the neutral setting, but that didn't solve my current problem.
I now wound up writing my own platform movement action, with good (and simple) acceleration and deceleration, a momentum setting and bool that allows me to suspend the entire thing. I also built a coroutine into it that switches the suspension off after a specified amount of time. So, e.g. that when I want to dash, switch the suspension on for a few frames, and it switches it off automatically.
But the kicker is this: somehow my action doesn't need my suspension setup, as I found out moments ago. Somehow, in my action, it does Set Velocity, but Add Force is not canceled. Don't know why. For now, it's sorcery but I am happy with the outcome because that makes things a lot easier.
