Is it just me? I'm testing out some MD2 model anims in Away3DLite - ones that I know loop well in Away3D - and the anims seem to be jumping at the loop point. It seems that the mesh positions are tweened between apart from on the loop point.
The first issue I noticed was that the anim names for referencing the anim frames seem to be slightly different, in that some characters are missing. "run" becomes "ru" or even "r" on some models. Is there a problem with the parser here? I'm trying to get my walk/run sequences working smoothly and failing horribly. Rather than reference the anim name I've tried looping (_mesh.loop(40,45)) - but I get the same results. Anyone got any idea what is happening? Is this a known problem that has a solution in a branch? Thanks in advance.
