bpy.data.meshes.new_from_object()
even when the mesh Object is not evaluated
Doing an initial check of the imported value should be fairly simple, and I can probably add a warning to print to the console if the imported weight lies outside of Blender's hard [-10, 10] range…
It's not the order of the checks that is changed here, in the ncase_cmp
case, I've changed it so that only bpy.path.resolve_ncase
is called because the first thing bpy.path.resolve_ncase
…
I profiled this particular fbx import with the cProfile
module on a locally built release build with the use_image_search
argument of bpy.ops.import_scene.fbx
set to False (it does a…
In the .fbx itself, the vertex order is consistent regardless of triangulation (it matches Blender's vertex order). I would guess the software you're importing into is reordering the vertices…
I almost exclusively model with quads such that if the triangulation ends up being important then it means I've messed up my topology and need to redo some of it, so I'm not really sure in what…
For only the purpose of getting existing attributes I think it would work well, but sometimes the attributes need to be created if they don't exist at which point the attributes
(AttributeGroup
…
I have made a PR to fix this.
This patch is deliberately separate from the other patches that update property access to use the newer attribute equivalents because those are (currently) only performance and future-proofing…