Hey Khaydar, sorry to hear this.

My best guess without seeing it would be that the translation of the legs (away from x=0) is written into some lesser-used property in the fbx that the tc3d generator does not read*.

(* Aside: one of the annoying things about FBX is there are lots of ways of achieving the same thing when it comes to positioning and it sometimes writes these into different properties. I've tried to support as many of these as possible, however if the property is blank it doesn't write it out. Therefore there could be a property that I've literally never encountered before!)

Annoying as this is, your fastest solution might be to try to get that translation into the "normal" place that the tc3d generator does read.

I can see you've modelled quite a few animals previously. Does the setup of these new animals differ to your previous animals in the structure of the bones/joints? I think normally my animal modeller has a root bone at 0,0,0 and everything else is based off this.

Happy to keep workshopping (no pun intended) this problem if you could investigate a bit and come back to me with what you find.

Good luck!

Fixed it by changing the bone coordinates to something else in the fbx. Interestingly I've ran into that issue a couple of time in the past, and it's always a leg bone of a quadruped animal. Something about the way I make skelettons, copy pasting leg bones is a big no apparently.