Hi,

I realize the proposal was harsh, but it was meant as a public statement as well
(to khronos, opencollada team, etc). I don't want to blame it on the hard
working devs here. We do have collada IO work at some level, and that has been
proven useful in several cases. The job is just incredible hard to achieve.

To move forward:

- userts who successfully applied .dae could also check whether another exchange
format would have done the job as good. Tried FBX?

- note that for basic mesh (+uv) export, a quite simple script could do the job
already. It is probably a few days job for a py scripter.

- we are currently including about 100 MB of opencollada libs to make a feature
work that's meant to be able to exchange (I+O) full shots or game environments,
with character animation and so on. That's what Collada was designed for, and
that's a target we can't support.

-Ton-

On 6 Jan, 2012, at 21:21, Morten Mikkelsen wrote: