This module provides access to blenders bmesh data structures.
This API gives access the blenders internal mesh editing api, featuring geometry connectivity data and access to editing operations such as split, separate, collapse and dissolve.
The features exposed closely follow the C API, giving python access to the functions used by blenders own mesh editing tools.
For an overview of BMesh data types and how they reference each other see: BMesh Design Document .
Disk and Radial data is not exposed by the python api since this is for internal use only.
This API is still in development and experimental, while we don’t expect to see large changes, many areas are not well tested yet and so its possible changes will be made that break scripts.
Campbell Barton, 13, March 2012
TODO items are...
# This example assumes we have a mesh object selected import bpy import bmesh # Get the active mesh me = bpy.context.object.data # Get a BMesh representation bm = bmesh.new() # create an empty BMesh bm.from_mesh(me) # fill it in from a Mesh # Modify the BMesh, can do anything here... for v in bm.verts: v.co.x += 1.0 # Finish up, write the bmesh back to the mesh bm.to_mesh(me)
There are 2 ways to access BMesh data, you can create a new BMesh by converting a mesh from bpy.types.BlendData.meshes or by accessing the current edit mode mesh. see: bmesh.types.BMesh.from_mesh and bmesh.from_edit_mesh respectively.
When explicitly converting from mesh data python owns the data, that is to say - that the mesh only exists while python holds a reference to it, and the script is responsible for putting it back into a mesh data-block when the edits are done.
Note that unlike bpy, a BMesh does not necessarily correspond to data in the currently open blend file, a BMesh can be created, edited and freed without the user ever seeing or having access to it. Unlike edit mode, the bmesh module can use multiple BMesh instances at once.
Take care when dealing with multiple BMesh instances since the mesh data can use a lot of memory, while a mesh that python owns will be freed in when the script holds no references to it, its good practice to call bmesh.types.BMesh.free which will remove all the mesh data immediately and disable further access.
When writing scripts that operate on editmode data you will normally want to re-calculate the tessellation after running the script, this needs to be called explicitly.
BMesh has a unified way to access mesh attributes such as UV’s vertex colors, shape keys, edge crease etc.
This works by having a layers property on bmesh data sequences to access the custom data layers which can then be used to access the actual data on each vert/edge/face/loop.
Here are some examples ...
uv_lay = bm.loops.layers.uv.active for face in bm.faces: for loop in f.loops: uv = loop[uv_lay] print("Loop UV: %f, %f" % (uv.x, uv.y))
shape_lay = bm.verts.layers.shape["Key.001"] for vert in bm.verts: shape = vert[shape_lay] print("Vert Shape: %f, %f, %f" % (shape.x, shape.y, shape.z))
# in this example the active vertex group index is used, # this is stored in the object, not the BMesh group_index = obj.vertex_groups.active_index # only ever one deform weight layer dvert_lay = bm.verts.layers.deform.active for vert in bm.verts: dvert = vert[dvert_lay] if group_index in dvert: print("Weight %f" % dvert[group_index]) else: print("Setting Weight") dvert[group_index] = 0.5
When modeling in blender there are certain assumptions made about the state of the mesh.
To give developers flexibility these conventions are not enforced, however tools must leave the mesh in a valid state else other tools may behave incorrectly.
Any errors that arise from not following these conventions is considered a bug in the script, not a bug in blender.
As mentioned above, it is possible to create an invalid selection state (by selecting a state and then de-selecting one of its vertices’s for example), mostly the best way to solve this is to flush the selection after performing a series of edits. this validates the selection state.