game-editor.com

Hello gE community, if someone could help me out with this very frustrating problem, I would be very appreciative! Throughout working on my game, I've constantly been dealing with this very annoying problem. Nearly every time my player starts an animation, he will start on the last frame, then jump to the first frame and play all the way through except the last frame. So if there's an animation that is five frames, he will start on the 5th, go to the 1st, 2nd, 3rd, and end on the 4th. This is obviously wrong.

This problem can be extremely annoying for certain animations. Animations like throwing always start off with his arm being in the wrong place... And I don't know why this problem is occurring, but I need to get it fixed. I use the state method for all my player's animations, and with all my functions for ChangeAnimation, I have FORWARD set. All my sprite sheets look similar to other people's, and even if my sprite sheets were weird, gameEditor shouldn't start it off on the last frame.

Does anyone have any idea what this problem is? Please help me with this, I really want to get this solved once and for all.

try using the NO_CHANGE state instead of the FORWARD state?

i never really use the FORWARD state!

if it doesn't work let me know, im more than willing to look over it for you if it comes down to it

So far the game seems to be working with NO_CHANGE. What does FORWARD do? And what does NO_CHANGE do? Does NO_CHANGE continue off of whatever frame number the last animation was on, so if you're in the middle of an animation like frame 5, and the animation changes, will it jump to the fifth frame in the next animation? I'm not sure if it does that, maybe it just means that the sprite sheet runs correctly like there's no change with the sprite sheet's order.

Thanks for the help though!

NO_CHANGE is for when you want to change an animation without resetting the current frame!

and your welcome im glad to help

FORWARD fixes the problem

FORWARD fixes the problem

actually the FORWARD state was what was giving him problems, the NO_CHANGE state fixed it