3D model painpoints

Currently there are some issues with the official 3D model that keep me and other users from updating to it from the sdk v1 addon to it. I'm writing this here in hopes it can be prioritized.

SCALING: most of the times developers author their 3d models to scale in their software. Meaning different models all have the correct relative scale, correct texel size etc. This is generally important but critical for modular kits (e.g. wall pieces that snap together). Currently Construct uses scale base on the bounding box, which doesn't work with this common workflow, the expected behavior is that a model at scale 1,1,1 it will match all other models at scale 1,1,1 the way they match in the 3d software they were made in.

ANIMATION BLENDING: blending between animations is very important to make animations look good, animation transitions look janky without it.

In general, making any transformations relative to the bounding box when it comes to 3d models is just asking for issues. All adjustments should be done in relation to the origin.

As for the issues this causes:

-as fedca wrote, due to the bounding box-based resizing method, model pivots do not align to the "container 3D Model" pivot. The adjustments in 3D Model (left/middle etc.) do not help because they are based on the bounding box...

-axis flipping is supported, but what is really needed is rotation as some software is Z-up, some is Y-up. Well, there is a rotation option in the imported file properties (not the one in 3D Model), but it still rotates around the bounding box center.