pymel.core.modeling.polyBevel¶

polyBevel(*args, **kwargs)¶

Bevel edges.

Flags:

Long Name / Short Name		Argument Types	Properties
angleTolerance / at		float
	Angular tolerance for creation of extra triangles Note this attribute is for compatability only and should not be modified in Maya 7.0 files Default:20.0
autoFit / af		bool
	If autoFit is on, it computes a smooth roundness : new facets round off a smooth angle. Default:true
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.
fillNgons / fn		bool
fraction / f		float
frozen / fzn		bool
maya2015 / m15		bool
mergeVertexTolerance / mvt		float
	Tolerance within which to merge vertices Default:0.0
mergeVertices / mv		bool
	Merge vertices within a tolerance Default:false
miteringAngle / ma		float
	Miter faces that have angles less than this value Default:0.0
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
offset / o		float
	The offset for bevel. Default:0.2
offsetAsFraction / oaf		bool
	If on, the offset value is treated as a fraction between zero and one. Default:false
roundness / r		float
	The roundness of bevel, it is taken into account when autoFit is off. Default:0.5
segments / sg		int
	The number of segments used for beveling. Default:1
smoothingAngle / sa		float
	Create new edges as hard edges if the angle between adjacent faces exceeds this value Default:0.0
subdivideNgons / sn		bool
	Subdivide new faces with more than 4 edges Default:false
useLegacyBevelAlgorithm / com		bool
	If on, bevel is done the way maya 2014 did Default:false
uvAssignment / ua		int
	Technique used to compute UVs on new faces 0 computes new UVs by projecting along surface normal of original mesh onto new mesh 1 computes new UVs by projecting along surface normal of new mesh onto original mesh Default:0
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.polyBevel

Example:

import pymel.core as pm

# Replace an edge by 1 face, the width of the new face is given by the offset value.
pm.polyCube( n='plg' )
pm.polyBevel( 'plg.e[7]', offset=0.2 )
pm.delete( 'plg' )

# Replace an edge by 4 faces, the new faces are rounding a smooth angle.
pm.polyCube( n='plg' )
pm.polyBevel( 'plg.e[7]', segments=4, offset=0.4 )
pm.delete( 'plg' )

# Replace an edge by 4 faces, the new faces are rounding an angle specified by the default value of roundness (i.e 0.5).
pm.polyCube( n='plg' )
pm.polyBevel( 'plg.e[7]', segments=4, autoFit=Flase )
pm.delete( 'plg' )