View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0023732||Runner||[All Projects] General||Public||2016-09-19 17:37||2018-06-18 09:52|
|Priority||None||Severity||C - General||Reproducibility||<25%|
|Target Version||Fixed in Version|
|Summary||0023732: skeleton_animation_set_ext() does not restart animations correctly|
|Description||Due to the documentation, skeleton_animation_set_ext() should work exactly like skeleton_animation_set_() , unless that the last command always use automatically track 0.|
But it turned out, that skeleton_animation_set_ext() does not restart an animation correctly, which was stopped with skeleton_animation_clear(0);, while this works with skeleton_animation_set_() properly.
Seems to me, as if
skeleton_animation_clear(track) has no effect for an animation started
with skeleton_animation_set_ext(animname, track). But it should has, as a
controlled beginning of such an animation is important for the graphical
In the meantime I solved the issue.
What I found out, is:
starts an animation always at frame 0.
So this will have no effect, the animation starts nevertheless at frame 0:
You can however start an animation at frame 20 with this code:
To make things more irritating,
does NOT start automatically at frame 0, but it takes the image_index,
which is set, when it comes next to drawing.
will next start the animation at track 0 with frame 20.
Also several animation on different tracks will always start at the same
image_index =20;//this overrides code before: image_index =10;
image_index =15;//this overrides code before: image_index =20;
All three animation will next start at the last set frame-value, which is
You can stop animations running on different tracks at different frames
The animation on this track freezes at the currently reached image_index.
But this does not stop image_index from furtherly being automatically
upcounted in every step.
is executed and no setting for image_index was done, the animation starts
at the currently reached
image_index, which gives the thing a random appearance.
This was the object of my bug-report.
|Additional Information||Original helpdesk ticket: http://help.yoyogames.com/tickets/110615|
|1.4 Found In||1.4.1760|
|2.x Runtime Found In|
|2.x Runtime Verified In|