1. Identifying the Bundle Problem
My initial assumption was that the FBX exporter would naturally respect the hierarchy or object selection. Instead, every export action was dumping the entire scene collection into a single file.
The issue isn't a setting deep in the render engine, but rather the default behavior of the FBX exporter. Without explicit instruction, Blender assumes the user wants the entire project state transferred.
- Enabled the standard FBX add-on.
- Verified all meshes were distinct objects.
- Confirmed the file size was bloated by unnecessary scene data.
2. Testing Selection-Only Export
My first instinct was to use the 'Selected Only' toggle within the export menu. This works perfectly for one or two meshes, but it is not a scalable solution for a character rig consisting of twenty individual parts.
I validated that this method does produce clean, isolated files, confirming that the export logic itself handles individual objects correctly. The bottleneck was entirely administrative.
- Select desired mesh in the viewport.
- Navigate to File > Export > FBX.
- Toggle 'Selected Objects' in the right-hand panel.
- Repeat manually for every single mesh.
3. Automating the Pipeline with Scripts
To save time, I moved to an automated approach. I found a utility script that loops through the scene objects and triggers the exporter individually for each one.
Installing this was straightforward once I bypassed the confusion of where to place custom python files. I saved the script locally, pointed the add-on installer to that path, and verified it in the toolshelf.
- Download the script as a .py file.
- Use Edit > Preferences > Add-ons > Install.
- Locate the new panel in the 3D viewport sidebar.
- Define the target output folder.
4. Confirming Unity Compatibility
After the batch process finished, I dragged the resulting files into my Unity project. Each FBX arrived as a clean, single-mesh asset, ready for materials and colliders.
This verification step is crucial. I checked the pivot points to ensure the automated export didn't reset the origin locations, which is a common failure point in scripted exports.
- Check object origins in Blender before exporting.
- Validate pivot point alignment inside Unity.
- Confirm mesh naming matches the Blender object name.
FAQ
Why not just export as OBJ?
While OBJ files work for simple meshes, they do not support advanced features like bones or vertex weights, which are necessary for most game assets.
Does the script handle nested object hierarchies?
Standard batch exporters usually flatten the hierarchy to ensure the mesh stays independent; always check the script settings if your asset relies on complex parent-child relationships.