You might be better off calculating the number of run cycles (and current phase) based on how far your running guy has traveled (assuming he always goes in the same direction). Actually, that would be a fun expression. Kind of like calculating the rotation of a wheel based on distance traveled, only more complicated. 🙂
You might be better off calculating the number of run cycles (and current phase) based on how far your running guy has traveled (assuming he always goes in the same direction). Actually, that would be a fun expression. Kind of like calculating the rotation of a wheel based on distance traveled, only more complicated. 🙂
What you’re seeing is a little difficult to explain but let me give it a shot. At any given frame, your expression picks up the current value of your speed slider and uses that to calculate the positon of your layer. The result you get is the same as if you had hard-coded that slider value into the expression. That is, at each frame, the calculation acts as though the slider has always been at its current value. Previous slider values have no effect on where the layer ends up – only the current value. Getting around this with an expression is a little complicated. Why not just parent your layer to a null and rotate the null?
What you’re seeing is a little difficult to explain but let me give it a shot. At any given frame, your expression picks up the current value of your speed slider and uses that to calculate the positon of your layer. The result you get is the same as if you had hard-coded that slider value into the expression. That is, at each frame, the calculation acts as though the slider has always been at its current value. Previous slider values have no effect on where the layer ends up – only the current value. Getting around this with an expression is a little complicated. Why not just parent your layer to a null and rotate the null?