Some Meshes incorrectly transformed in Blender 3.4, but not in 2.83

[Pherakki]

In C0001_101_00.GMD, the pyramids attached to the elbows are correctly transformed to their respective bones in Blender 2.83 - but they remain at the origin in Blender 3.4.

Related to #19.

[Pherakki]

Another instance: mesh_12 (skirt mesh) is incorrectly deformed in the bind pose in Blender 3.4 for C0004_001_00.GMD, but it is ok in Blender 2.83. Appears to be another victim of an incorrectly-transformed mesh.

[Pherakki]

Further notes: This may have something to do with a difference in the way Blender 3.4 constructs the armatures.

In Blender 2.83:

• Switching off the influence of the Copy Transforms constraints does not move the bones on a Pinned Armature
• Meshes remain in the same position in Edit Mode

In Blender 3.4:

• Switching off the influence of the Copy Transforms constraints causes the bones to move back to where their positions would be if the armature was situated at the origin
• Meshes transform back to where they would be if their parent Pinned Armature was at the origin

Presumably some of the transform commands are not being interpreted in the same way between Blender 2.83 and Blender 3.4. Needless to say, the plugin needs to be fixed so that the 2.83 behaviour is reproduced in 3.4.

[Pherakki]

Partial fix in 945b78cfebf1cfd12f35503d32ec8122e843e74e: Bones and Meshes no longer transform back to their "origin-relative" positions. However, some bones calculate the incorrect roll still.

[Pherakki]

Appears to now be fixed in 40a96c6: Blender 3.4 seems to disagree with Blender 2.83 on what the value of the bone roll should be in the pinned matrices. Manually setting the value of the bone's matrix seems to fix, but this is slightly disturbing and should be understood to make sure there's no weird bugs introduced by this.