Go to: Synopsis. Return value. Related. Flags. MEL examples.

Synopsis

polyMergeVertex [-alwaysMergeTwoVertices boolean] [-caching boolean] [-constructionHistory boolean] [-distance linear] [-mergeToComponents string] [-name string] [-nodeState int] [-texture boolean]

polyMergeVertex is undoable, queryable, and editable.

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.

Return value

string The node name.

In query mode, return type is based on queried flag.

Related

polyCloseBorder, polyCollapseEdge, polyCollapseFacet, polyDelEdge, polyDelFacet, polyDelVertex, polyMergeEdge, polyMergeFacet, polyQuad, polyReduce, polySewEdge

Flags

alwaysMergeTwoVertices, caching, constructionHistory, distance, mergeToComponents, name, nodeState, texture
Long name (short name) Argument types Properties
-distance(-d) linear createqueryedit
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.
-alwaysMergeTwoVertices( -am) boolean createqueryedit
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.
-texture(-tx) boolean createqueryedit
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.
-mergeToComponents(-mtc) string createqueryedit
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.
Common flags
-name(-n) string create
Give a name to the resulting node.
-constructionHistory(-ch) boolean createquery
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.
-caching(-cch) boolean createedit
Toggle caching for all attributes so that no recomputation is needed
-nodeState(-nds) int createqueryedit
Defines how to evaluate the node.
  • 0: Normal
  • 1: PassThrough
  • 2: Blocking
  • 3: Internally disabled. Will return to Normal state when enabled
  • 4: Internally disabled. Will return to PassThrough state when enabled
  • 5: Internally disabled. Will return to Blocking state when enabled
Flag can appear in Create mode of command Flag can appear in Edit mode of command
Flag can appear in Query mode of command Flag can be used more than once in a command.

MEL examples

 polyPlane -sx 5 -sy 5 -n plg1;
 polyPlane -sx 5 -sy 5 -n plg2;
 move -ws 0.55 0 -1.25 plg1; move -ws -0.55 0 -1.25 plg2;
 polyPlane -sx 5 -sy 5 -n plg3;
 polyPlane -sx 5 -sy 5 -n plg4;
 polyPlane -sx 5 -sy 5 -n plg5;
 move -ws 0.55 0 1.25 plg4; move -ws -0.55 0 1.25 plg5;

 // First method:
   polyUnite plg1Shape plg2Shape;
   select -r polySurface1.vtx[6] polySurface1.vtx[12]
       polySurface1.vtx[18] polySurface1.vtx[24]
       polySurface1.vtx[47] polySurface1.vtx[53]
       polySurface1.vtx[59] polySurface1.vtx[65];
   polyMergeVertex -d 0.15;

   // <i>Second method</i>:
   polyMergeVertex -d 0.25 plg3.vtx[24] plg3.vtx[30:31]
       plg3.vtx[8:10] plg3.vtx[14:16]
       plg3.vtx[20:22];

// To create non-manifold geometry:
   polyUnite plg4Shape plg5Shape;
   select -r 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];
   polyMergeVertex -d 0.25;
 // Note that there is only one vertex at this merged point and the
 // resulting polygonal object is non-manifold;

        // Merge some verts to the center of some edges
        select -all; delete;
        polyPlane -w 10 -h 10 -sx 10 -sy 10 -ax 0 1 0 -cuv 2 -ch 1;
        select -r pPlane1.vtx[8] pPlane1.vtx[12] ;
        polyMergeVertex -mergeToComponents "pPlane1.e[183] pPlane1.e[162] pPlane1.e[166] pPlane1.e[187]" -d 0.0001 -am 0 -ch 1;