animation loop hitch.
mrsclean
Member Posts: 1
Hi all,
I've been trying out GameSalad over the past day or so, trying to get to know its quirks and capabilities. So far, it seems pretty straight forward, and the community responses are a great resource. That said, I've run into something that is puzzling me.
I have a main animated figure that turns into another figure when swiped. For example: Face 1... swipe left triggers a transition animation to face 2. So far so good. It functions fine, but I'm getting a little "hitch" between animations... and I don't know if that is me, or just a limitation of GameSalad.
My approach has been to use a main invisible actor containing swipe recognition which in turn sets a conditional attribute (an integer from 1-12). Then, I have a series of actors that respond to the changed attribute by first turning itself visible, running through its animation (using a timer), changing the attribute to trigger the next animation, and turns the actor invisible again.
As I said, I have it all working fine, except a "blip" after each animation finishes, and the next animation starts. I've tried eliminating timers by referencing frame played, I've adjusted the timer to make sure that its not a mismatch between my animation frame rate and timer... to no avail.
So, I was assuming that I'm just being clumsy in how I structured the logic... rather than there being something inherently slow about collecting swipe data, having it change an attribute, then in a different actor, using that changed attribute to turn it visible/invisible.
Any insights on why it might be "catching" would be appreciated. Thanks.
I've been trying out GameSalad over the past day or so, trying to get to know its quirks and capabilities. So far, it seems pretty straight forward, and the community responses are a great resource. That said, I've run into something that is puzzling me.
I have a main animated figure that turns into another figure when swiped. For example: Face 1... swipe left triggers a transition animation to face 2. So far so good. It functions fine, but I'm getting a little "hitch" between animations... and I don't know if that is me, or just a limitation of GameSalad.
My approach has been to use a main invisible actor containing swipe recognition which in turn sets a conditional attribute (an integer from 1-12). Then, I have a series of actors that respond to the changed attribute by first turning itself visible, running through its animation (using a timer), changing the attribute to trigger the next animation, and turns the actor invisible again.
As I said, I have it all working fine, except a "blip" after each animation finishes, and the next animation starts. I've tried eliminating timers by referencing frame played, I've adjusted the timer to make sure that its not a mismatch between my animation frame rate and timer... to no avail.
So, I was assuming that I'm just being clumsy in how I structured the logic... rather than there being something inherently slow about collecting swipe data, having it change an attribute, then in a different actor, using that changed attribute to turn it visible/invisible.
Any insights on why it might be "catching" would be appreciated. Thanks.
Comments
Guru Video Channel | Lost Oasis Games | FRYING BACON STUDIOS