yeah Richard I will, but I'm still looking at it. It's apparently not consistent. Another thing I came across is a name occurring like mesh. 12 which isn't the twelfth mesh but appears to be a string concatenation of mesh.1 + 2.
On May 23, 1:17 am, richardolsson <[email protected]> wrote: > Hood catch. Probably a faulty implementation in the parser. Any chance > you could post this on the issue tracker on > github?https://github.com/away3d/away3d-core-broomstick/issues > > Cheers > > On May 23, 4:13 am, Choons <[email protected]> wrote: > > > > > > > > > Been looking at the md2 loader examples and noticed the trace on > > event.asset.assetType always seems to fire twice for a single md2 > > mesh. Tracing the name of the mesh shows 'mesh' and 'mesh.2' (btw > > thanks to the devs for adding that default name functionality!). It > > doesn't really seem to affect how the app runs, but I'm just curious > > what is happening there.
