Yes. Discussed in "Things You May Not Know" thread.
Except if you test with any vertical KO move, like in mixa's post, this is shown to be clearly wrong.
I was confused at first because I didn't understand how the formula worked, but after a while of debugging, I finally understand it now.
The damage of the move is part of the equation. A 15 damage attack vs a 20 damage attack, makes a significant difference in the total knockback. Really, I think it's just a misunderstanding of words. I guess that Toomai wanted to make it clear that the only difference when it comes to staleness is the damage part of the formula.
The way knockback physics work is, it calculates based on the formula in the picture. After that, you factor in angle for the X and Y knockback velocity. So you just get that number you got from doing the formula and then multiply with sin(angle) to get the Y Knockback velocity and cos(angle) to get the X knockback velocity. Then all that's left is acceleration / deceleration. So far I've paid more attention to Y velocity, since I wanted to understand the fall speed mechanics, so I don't fully know about the acceleration of X. Keep in mind there's 2 different velocities for X and Y. There's a knockback velocity and a jumping / falling velocity. When you get hit, your regular Y velocity starts at 0 and then keeps subtracting by your fall speed acceleration, until you reach your max fall speed. So every frame you add Knockback velocity to your Y coordinates and also subtract from the other Y velocity.
Here's a run down of the whole formula. I'll use Fox's Uair vs Mario as an example, and assume it's fresh. Lets say Mario has 70 damage before getting hit. First hit of Uair will do 2 damage, second hit will do 13 damage. Second hit has an angle of 90 and a knockback of 135. You plug in the 13 damage into formula and you end up with a total of 144.7875. Then for Y knockback velocity, you multiply 144.7875 with sin(90) (which happens to be 1.0). Note that everytime you get hit, your falling velocity automatically goes to 0. Now, all that's left is acceleration and deceleration. In the updating process of the Y coordinate during each frame, you add Y-Knockback velocity to the Y Coordinate, then subtract (1.7 x sin(angle)) to knockback velocity, then you subtract falling velocity by fall speed acceleration and subtract Y Coordinate with fall speed acceleration. When the character reaches max fall speed, then you stop subtracting Y velocity by fall speed acceleration.
I didn't write down the exact order when it came to adding and subtracting for acceleration and deceleration, but you get the general idea.
Now if you were to do Fox's U air vs Mario at 70 damage before getting hit while it's stale, the velocity would be 117.288 instead of 144.7875, so that would be the difference between fresh and stale.
