This goes for other big old gnarly composite or specialty files which I don't expect Unity to support directly, or the way I want them supported. Maybe the dummy character is wearing all his clothes and holding several kinds of weapons. Maybe the house is made in Blender with 50 pieces, and I export them room by room into 4 FBX files. I can then decide manually which pieces get exported as separate FBX files, and then put those FBX files into Unity's clutches within the Assets tree. I would much rather take a big old gnarly composite file such as one blend with a complete house or a complete character with an extensive wardrobe, and keep it OUT of the Assets folder. Even if Unity is launching Blender and asking Blender to export to FBX, it's expecting too much to assume I can tell Unity exactly how each FBX should be exported with all the settings available. Click to expand.This is true, but having worked with Blender for many years, inside its Open Source code and also as a modeling user, I really really don't like to assume that any other app should try to import the file themselves.
