I know there is a problem with md2 export from milkshape that in the parsed 
name some invalid characters are inserted. I hacked the parser to clean that 
mess which seems comes from the md2 itself. The rest of stuff , like anim 
sequences switching works all right . 

Sent from my iPhone

On Aug 21, 2010, at 8:46 PM, katopz <[email protected]> wrote:

> my last test (a sec ago) via branches is working fine with md2 from quake, so 
> it's may be exporter problem?
> what's your exporter btw? you can send md2 off list to me, i'll see what i 
> can do
> 
> On 22 August 2010 00:22, Swingpants <[email protected]> wrote:
> 
> 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.
> 
> 
> 
> -- 
> Regards
> -----------------------------------------------------------
> Todsaporn Banjerdkit, katopz, http://sleepydesign.com
> Away3DLite and JigLibFlash Developer Team

Reply via email to