Non orthogonal matrix support

[Anonymous]

Hello there!

I recently rigged and animated a model for my project, but when I tried to export it I got this error:

One or more objects in the scene has local axes that are not perpendicular to each other (non-orthogonal).
The FBX plug-in only supports orthogonal (or perpendicular) axes and will not correctly import or export any transformations that involve non-perpendicular local axes.
This can create an inaccurate appearance with the affected objects:
-Rig1LDigit11LH
-Rig1LDigit12LH
-Rig1LDigit21LH
-Rig1LDigit22LH
-Rig1RDigit11RH
-Rig1RDigit12RH
-Rig1RDigit21RH
-Rig1RDigit22RH

All those bones belong to the hands of my character. How can I fix it? Many thanks.

[miledrizk]

Hi,

I made this video recently to explain how to solve this problem, and also

I explained what it means and what are the scenarios that might cause this issue.

https://youtu.be/GU7Q4tMzdPk

[Anonymous]

When I change the values they just instantly snap back to what they were originally is there any fix for this or reason this is happening?

[alex.georgiev94]

Hey,

I usually go about fixing this error like this: Press on Utilities > Reset XForm > Reset Selected. 

Hope this helps 🙂

[Diffus3d]

Hello @Anonymous ,

Alfred here, happy to try to help.  You're probably going to need to double check every bone and the root for any transform information.  Maybe also check rig controllers if you have some, but I'm not sure if that part matters.  In this case with the original user it was his hands but it may very well be an ankle in your scene, the root, a minor finger digit...  If you've check them all and still get the error, then possibly the rig is parented to a master mover of some kind?  Make sure that doesn't have transform history either.  

Does that make sense?

Best Regards,

[m010753j]

I tried both methods in your video and it did not work. The weird thing is, the second method in your video has worked before for an old project but now it just won't let me change the scale

[adam.breen]

I had the same error on 2025.2 on a static mesh. Freezing all transformations fixed it for me