Many of these exchange file formats originate from the fixed GPU pipeline era of materials, and there are simply no data structures in their specifications to accommodate that type of data, let alone all possible types of properties, settings or exotic combinations of maps.
Marmoset toolbag safe frame full#
These are mostly mesh-only, geometry-centric file formats concerned with porting object shapes, and some times animation, armature, and basic shading, or color properties (like MTL files) never full complex material definitions. You can't, for the most part, import/export material definitions between applications, you can't even get Blender Internal Materials to work with Cycles Renderer nor vice versa, and they are both created within Blender, let alone between completely different applications.įor this reason no file format you use can, or even tries to, import or export material properties, be it 3DS, FBX, Collada, STL, OBJ or any other. Materials are too implementation specific and tightly tied to the rendering system they belong to, or software they were created with. Manually reproduce your materials using available textures at the target environment. Also most Blender importers/exporters don't currently support node based materials well.
Most file formats just don't support exporting textures, let alone full blown material definitions or other application specific features.
0 kommentar(er)
