❌ Don’t rely on collection activation checkboxes They mean nothing to the export tool. Only the 👁️ eye icon matters. If it’s not visible, it won’t go. ❌ Don’t nest a dozen Empty objects as parents Multiple levels of nested empties are not handled. Keep your parenting reasonable. We’re exporting models, not family trees. ❌ Don’t forget to apply transforms Seriously. If we see another upside-down, 200-meter tall cube in Unity, we riot. ❌ Don’t rename files as Final_v2_THIS_IS_IT_3_really.fbx The exporter uses collection or object names, so name things properly in Blender. Avoid future shame. ❌ Don’t expect the add-on to fix your bad UVs If you don’t have a second UV map, the add-on won’t magically create one. Go make it. Now. ❌ Don’t export while in Edit Mode Always be in Object Mode. Blender gets grumpy otherwise, and your exports might fail silently.

Most likely: Transforms weren’t applied (location/rotation/scale) You messed up Forward/Up axes Use -Z Forward, Y Up for Unity, and enable Apply Transforms. You're welcome.

Because you didn’t set an export path in the panel. Do yourself a favor — set it once, save your file, and move on.

Separate Child Collections = each child collection gets its own FBX in a subfolder Combine Nested Collections = all child objects get squished into a single FBX named after the parent They don’t play together. If “Combine” is on, it wins.

Because at least one of your meshes has less than 2 UV channels. If you're heading into game engine territory (hello, lightmaps), you need a second UV map. Fix it, or prepare for a world of unlit sadness.

Because only visible collections and objects (👁️ eye icon) are considered. The add-on ignores the "active" checkbox and camera icons in the outliner. If it’s not visible in the viewport, it's dead to us. Also, no support for multiple nested Empty parents — keep your hierarchies sane, please.