pymel.core.modeling.polyMergeVertex¶

polyMergeVertex(*args, **kwargs)¶

Merge vertices within a given threshold.Since this allows merging any vertices that lie on the same object it is possible for the resulting geometry to be non-manifold.First, perform comparison of pairs of selected vertices. Pairs that lie within given distance of one another are merged, along with the edge between them.Second, any selected vertices which share an edge are merged if the distance between them is within the specified distance.Unlike Merge Edges, Merge Vertices will perform the merge even if the edges adjoining the vertices do not have matching orientation (i.e. normals of adjacent faces do not point in the same direction). As this restriction is not enforced while merging vertices, resulting geometry can be non-manifold.If alwaysMergeTwoVertices is set and there are only two vertices, tolerance is ignored and the vertices will be merged.Resulting mesh may have extra vertices or edges to ensure geometry is valid.

Flags:

Long Name / Short Name		Argument Types	Properties
alwaysMergeTwoVertices / am		bool
	This flag specifies whether to always merge if only two vertices are selected regardless of distance. C: Default is false. Q: When queried, this flag returns a boolean.
caching / cch		bool
	Toggle caching for all attributes so that no recomputation is needed
constructionHistory / ch		bool
	Turn the construction history on or off (where applicable). If construction history is on then the corresponding node will be inserted into the history chain for the mesh. If construction history is off then the operation will be performed directly on the object. Note:If the object already has construction history then this flag is ignored and the node will always be inserted into the history chain.
distance / d		float
	This flag specifies the distance within which vertices will be merged. C: Default is 0.0 (i.e. vertices are coincident). Q: When queried, this flag returns a double.
frozen / fzn		bool
mergeToComponents / mtc		unicode
	Optionally defines the position to merge all of the vertices to. If set, the distance flag will be ignored, and instead the center point of the set components will be calculated and all vertices will be merged to that location. C: Default is empty string. Q: When queried, this flag returns a string.
name / n		unicode
	Give a name to the resulting node.
nodeState / nds		int
	Maya dependency nodes have 6 possible states. The Normal (0), HasNoEffect (1), and Blocking (2)states can be used to alter how the graph is evaluated. The Waiting-Normal (3), Waiting-HasNoEffect (4), Waiting-Blocking (5)are for internal use only. They temporarily shut off parts of the graph during interaction (e.g., manipulation). The understanding is that once the operation is done, the state will be reset appropriately, e.g. Waiting-Blockingwill reset back to Blocking. The Normaland Blockingcases apply to all nodes, while HasNoEffectis node specific; many nodes do not support this option. Plug-ins store state in the MPxNode::stateattribute. Anyone can set it or check this attribute. Additional details about each of these 3 states follow. StateDescriptionNormalThe normal node state. This is the default.HasNoEffectThe HasNoEffectoption (a.k.a. pass-through), is used in cases where there is an operation on an input producing an output of the same data type. Nearly all deformers support this state, as do a few other nodes. As stated earlier, it is not supported by all nodes. Its typical to implement support for the HasNoEffectstate in the nodes compute method and to perform appropriate operations. Plug-ins can also support HasNoEffect. The usual implementation of this state is to copy the input directly to the matching output without applying the algorithm in the node. For deformers, applying this state leaves the input geometry undeformed on the output. BlockingThis is implemented in the depend node base class and applies to all nodes. Blockingis applied during the evaluation phase to connections. An evaluation request to a blocked connection will return as failures, causing the destination plug to retain its current value. Dirty propagation is indirectly affected by this state since blocked connections are never cleaned. When a node is set to Blockingthe behavior is supposed to be the same as if all outgoing connections were broken. As long as nobody requests evaluation of the blocked node directly it wont evaluate after that. Note that a blocked node will still respond to getAttrrequests but a getAttron a downstream node will not reevaluate the blocked node. Setting the root transform of a hierarchy to Blockingwont automatically influence child transforms in the hierarchy. To do this, youd need to explicitly set all child nodes to the Blockingstate. For example, to set all child transforms to Blocking, you could use the following script. import maya.cmds as cmds def blockTree(root): nodesToBlock = [] for node in {child:1 for child in cmds.listRelatives( root, path=True, allDescendents=True )}.keys(): nodesToBlock += cmds.listConnections(node, source=True, destination=True ) for node in {source:1 for source in nodesToBlock}.keys(): cmds.setAttr( ‘%s.nodeState’ % node, 2 ) Applying this script would continue to draw objects but things would not be animated. Default:kdnNormal
texture / tx		bool
	This flag specifies whether the texture is sewn in addition to the 3d edge C: Default is true. Q: When queried, this flag returns a boolean.
worldSpace / ws		bool
	This flag specifies which reference to use. If on: all geometrical values are taken in world reference. If off: all geometrical values are taken in object reference. C: Default is off. Q: When queried, this flag returns an int. Flag can have multiple arguments, passed either as a tuple or a list.

Derived from mel command maya.cmds.polyMergeVertex

Example:

import pymel.core as pm

pm.polyPlane( sx=5, sy=5, n='plg1' )
pm.polyPlane( sx=5, sy=5, n='plg2' )
pm.move( 0.55, 0, -1.25, 'plg1', ws=True )
pm.move( -0.55, 0, -1.25, 'plg2', ws=True )
pm.polyPlane( sx=5, sy=5, n='plg3' )
pm.polyPlane( sx=5, sy=5, n='plg4' )
pm.polyPlane( sx=5, sy=5, n='plg5' )
pm.move( 0.55, 0, 1.25, 'plg4', ws=True )
pm.move( -0.55, 0, 1.25, 'plg5', ws=True )

# First method:
pm.polyUnite( 'plg1Shape', 'plg2Shape' )
pm.select( 'polySurface1.vtx[6]', 'polySurface1.vtx[12]', 'polySurface1.vtx[18]', 'polySurface1.vtx[24]', 'polySurface1.vtx[47]', 'polySurface1.vtx[53]', 'polySurface1.vtx[59]', 'polySurface1.vtx[65]', r=True )
pm.polyMergeVertex( d=0.15 )

# Second method:
pm.polyMergeVertex( 'plg3.vtx[24]', 'plg3.vtx[30:31]', 'plg3.vtx[8:10]', 'plg3.vtx[14:16]', 'plg3.vtx[20:22]', d=0.25 )

# To create non-manifold geometry:
pm.polyUnite( 'plg4Shape', 'plg5Shape' )
pm.select( 'polySurface2.vtx[0]', 'polySurface2.vtx[6]', 'polySurface2.vtx[12]', 'polySurface2.vtx[18]', 'polySurface2.vtx[24]', 'polySurface2.vtx[30]', 'polySurface2.vtx[41]', 'polySurface2.vtx[47]', 'polySurface2.vtx[53]', 'polySurface2.vtx[59]', 'polySurface2.vtx[65]', 'polySurface2.vtx[71]', r=True )
pm.polyMergeVertex( d=0.25 )
# Note that there is only one vertex at this merged point and the
# resulting polygonal object is non-manifold;()