why does this 3ds export cock up so badly?
category: gfx [glöplog]
ok, thought just to give an update to this drivel: so, i researched all this a bit further:
- blender can export .fbx but gargaj says it's dated (didnt notice as it exported all basics that i needed)
- blender cant import .fbx unless you get the bratwurst-fork (LOL! now i know why xtrim likes the fbx format so much :P) and that fbx support is based on the assimp multi-poop-format-converter.
so, .dae it is. .fbx is fine for swapping inbetween autodesk products (max, mudbox), which i am doing. .dae for swapping inbetween autodesk (max) and nonautodesk (blender) products. ;)
and .3ds is broken shit. doesnt store normals afaik so whatever you end up with is just how the importing modelling package decides to interpolate vertex normals and their smooth groups.
ideally you have your own file format and exporter obviously, but it cant be christmas every day!
also you would suspect 2013AD (and after decades of commercial 3D) some decent standards would exist. :P
- blender can export .fbx but gargaj says it's dated (didnt notice as it exported all basics that i needed)
- blender cant import .fbx unless you get the bratwurst-fork (LOL! now i know why xtrim likes the fbx format so much :P) and that fbx support is based on the assimp multi-poop-format-converter.
so, .dae it is. .fbx is fine for swapping inbetween autodesk products (max, mudbox), which i am doing. .dae for swapping inbetween autodesk (max) and nonautodesk (blender) products. ;)
and .3ds is broken shit. doesnt store normals afaik so whatever you end up with is just how the importing modelling package decides to interpolate vertex normals and their smooth groups.
ideally you have your own file format and exporter obviously, but it cant be christmas every day!
also you would suspect 2013AD (and after decades of commercial 3D) some decent standards would exist. :P
