RESOLVED - Collada Import Mangled Since 1.0.1 - LOGGED

#1 Having a quick hand parse of the DAE,

Your up axis is along the Z (which matches Torque)

The rotation (axis angle) of each node are
Rotate Z = 0 0 1 0
Rotate Y = 0 1 0 0
Rotate X = 1 0 0 0
Which is identity except
Shape50 which is
Rotate Z = 0 0 1 0
Rotate Y = 0 1 0 0
Rotate X = 1 0 0 90
But I think that isn't the main tree model, so shouldn't affect things.

Tried loading it into another app, and it also shows it standing up, so Beta2 is looking shifty with a guilty look on its face.

I think you have yourself a genuine bug in Beta2!

HTH,
Deano

#2 Logged as TQA-814 for the QA team to verify.

#3 Hi Steve,

I think this is an issue with your model, albeit one that would only show up in T3D 1.1.

One of the improvements made to the collada loader in 1.1 was to import all transforms relative to the 'bounds' node. This is required to support ground transforms. If the model does not contain a 'bounds' node, this feature has no effect.

Your model's bounds node looks like this:

<translate sid="translate">0.00000 0.00000 0.00000</translate>
<rotate sid="rotateZ">0 0 1 0.00000</rotate>
<rotate sid="rotateY">0 1 0 0.00000</rotate>
<rotate sid="rotateX">1 0 0 90.00000</rotate>
<scale sid="scale">100.00000 100.00000 100.00000</scale>

ie. it has a 90 degree rotation around the X axis. When the model is imported by T3D, all transforms are relative to this basis, which effectively rotates your model -90 degrees around the X axis.

Fix it by removing the bounds node (if you don't need it, and just let the collada loader calculate the model bounding box automatically), OR by rotating the bounds node -90 around the X axis prior to export (ie. the bounds node will now have the identity transform).

#4 Result.
I had checked through everything else but it just never occurred to me to check my bounding box ...

Well spotted Chris, moving to resolved.

#5 Exporting relative to non parent node is a bug in your Collada importer, you need to change the code for ground transforms if its requiring it.

Collada is a standard you can't change a fundamental operation like parenting. The node hierarchy is clear in the file, its not a child of bounds therefore not altered by its transform. If ground transform rely on that, they need fixing or special casing is some way that doesn't potentially break in a odd hard to debug many legit models.

Deano