I am sorry to say that I don't know the dae format very well, but could it be that the default scale is [1,1,1] (implicit if not specified) and the plugin is expecting that to be the case for all shapes? (Since the SDK can't handle scale)
The reasons I can come to think of that might produce an erroneous rotation are:
1. scaled transforms
2. inverted transforms
(I started working, a long time ago now, on a version that should handle scaling to some extent, but as there hasn't been time to take care of that, perhaps I should instead focus on producing warnings when objects have scaled or inverted transforms... I'll add that to the TODO list)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
when exporting objects from max into collada dae files, we encounter the following problems.
under the node:
COLLADA/library_physics_models/physics_model/rigid_body/technique_common/shape
the scale factor (node "scale") for the collision shape is missing. Furthermore the rotation (node "rotate") seems to be wrong in some cases.
Any idea ?
Hi!
I am sorry to say that I don't know the dae format very well, but could it be that the default scale is [1,1,1] (implicit if not specified) and the plugin is expecting that to be the case for all shapes? (Since the SDK can't handle scale)
The reasons I can come to think of that might produce an erroneous rotation are:
1. scaled transforms
2. inverted transforms
(I started working, a long time ago now, on a version that should handle scaling to some extent, but as there hasn't been time to take care of that, perhaps I should instead focus on producing warnings when objects have scaled or inverted transforms... I'll add that to the TODO list)