I would suggest fixing the issues with the away3d parser so that it imports your model properly rather than writing xslt to hack around them.
-Ken On Sun, May 2, 2010 at 7:26 PM, valeriuscrowe <[email protected]>wrote: > I still don't have a working pipeline from 3ds Max 2010 to Away3D for > models of animated bipeds. These issues have been discussed here > several times, but now I have a hare-brained scheme to deal with it, > and I'm looking for feedback from the community. > > Many modeling and animation platforms will export Collada, and many > developers here seem to feel that the original Feeling Software > ColladaMax and ColladaMaya exporters are probably the most robust path > to get 3D into Away3D. However most or many of the other dialects of > Collada, such as the standard Autodesk exporters, seem to be either > brittle or unusable. > > So here's my thought. As long as all the data is somehow expressed in > the dialect of Collada that I'm dealing with, couldn't I write an XSLT > transform to get it into a format that Away3D likes? Does anyone know > which Collada exporters simply leave out necessary data, as opposed to > expressing it in a way that Away3D can't deal with? For example, > after looking at the files it looks to me like ColladaMax Nextgen has > all the data, but it's not expressed in the same way that Feeling > ColladaMax did. My hope is that most of the exporters are like that, > and with a little massaging I can take what they give me and rework it > to a format that Away3D likes. > > Thoughts? Ideas? Expert opinions? Volunteers to help develop it? > > Robert >
