[Bf-committers] Collada importer/exporter kickout

[Campbell Barton]

On Sun, Jan 8, 2012 at 12:03 AM, skoti <skoti48 at o2.pl> wrote:
> I know Collada importer / exporter is problematic (I wrote an importer
> for my engine and I know that everything in the Collada can be stored in
> N different ways).
>
> - If you want to use the model in Second Life / Google Earth, you have
> to use Collada, if you want to use models in engines WebGL/Flash3D
> practically have to use Collada (is there any web engine with FBX
> importer?), Most game engines use Collada for importing data (support
> for FBX a few). FBX exporter also has bugs. Well, that FBX is in a
> blender, but it is not usually an option for people using Collada.

Can you report these bugs please?

I'm no great fan of FBX/Autodesk with their idiotic EULA, but as
maintainer of FBX export I rather not have it be buggy.

Note that FBX has similar issues as collada, which is that different
applications support different parts of the FBX spec - so Lightwave
and Maya for example complain when importing non uniform scaled bones
from blender for EG because they don't support it.
So you cant assume just because a single application chokes on a
blender FBX model that it is a blender bug for sure.