Upload 19 files

array.rst.txt

@@ -0,0 +1,170 @@
+.. _bpy.types.ArrayModifier:
+
+**************
+Array Modifier
+**************
+
+The *Array* modifier creates an array of copies of the base object, with each copy being offset from
+the previous one in any of a number of possible ways. Vertices in adjacent copies can be merged if they are nearby,
+allowing smooth :doc:`Subdivision Surface </modeling/modifiers/generate/subdivision_surface>`
+frameworks to be generated.
+
+This modifier can be useful when combined with tileable meshes for quickly developing large scenes.
+It is also useful for creating complex repetitive shapes.
+
+Multiple Array modifiers may be active for an object at the same time
+(e.g. to create complex three-dimensional constructs).
+
+
+Options
+=======
+
+.. figure:: /images/modeling_modifiers_generate_array_panel.png
+   :align: right
+
+   The Array modifier.
+
+Fit Type
+   Controls how the length of the array is determined. There are three choices,
+   activating respectively the display of the *Curve*, *Length* or *Count* settings explained below:
+
+   Fit Curve
+      Generates enough copies to fit within the length of the curve object specified in *Curve*.
+   Fit Length
+      Generates enough copies to fit within the fixed length given by *Length*.
+   Fixed Count
+      Generates the number of copies specified in *Count*.
+
+.. container:: lead
+
+   .. clear
+
+.. note::
+
+   - Both *Fit Curve* and *Fit Length* use the local coordinate system size of the base object, which means that
+     scaling the base object in Object Mode will not change the number of copies generated by the modifier.
+   - *Fit Length* uses the local coordinate system length of the curve, which means that scaling the curve in
+     Object Mode will not change the number of copies generated by the modifier.
+   - :ref:`Applying <bpy.ops.object.transform_apply>` the scale can be useful for both.
+
+
+Offset
+------
+
+Constant Offset, X, Y, Z
+   Adds a constant translation component to the duplicate object's offset.
+   X, Y and Z constant components can be specified.
+
+Relative Offset, X, Y, Z
+   Adds a translation equal to the object's bounding box size along each axis, multiplied by a scaling factor,
+   to the offset. X, Y and Z scaling factors can be specified.
+
+   .. figure:: /images/modeling_modifiers_generate_array_offset-relative.png
+
+      Relative offset (0.5, 1.0 and 1.5) examples.
+
+Object Offset
+   Adds a transformation taken from an object (relative to the current object) to the offset.
+   It is good practice to use an Empty object centered or near to the initial object.
+   E.g. by rotating this Empty a circle or helix of objects can be created.
+
+   .. figure:: /images/modeling_modifiers_generate_array_offset-object.png
+
+      Object offset example.
+
+
+Merge
+-----
+
+Merge
+   If enabled, vertices in each copy will be merged with vertices
+   in the next copy that are within the given *Distance*.
+First Last
+   If enabled **and** *Merge* is enabled, vertices in the first copy will be merged with vertices
+   in the last copy, again if they are within *Distance* range. This is useful for circular objects.
+
+   .. list-table:: First Last merge example.
+
+      * - .. figure:: /images/modeling_modifiers_generate_array_first-last-off.png
+
+             Subdivision discontinuity caused by not merging vertices between first and
+             last copies (*First Last* off).
+
+        - .. figure:: /images/modeling_modifiers_generate_array_first-last-on.png
+
+             Subdivision discontinuity eliminated by merging vertices between first and
+             last copies (*First Last* on).
+
+Distance
+   Controls the merge distance for *Merge* and *First Last*.
+
+
+UVs
+---
+
+U Offset, V Offset
+   Shifts UVs of each new duplicate by a settable amount.
+
+
+Cap
+---
+
+Start Cap / End Cap
+   This allows either endpoints of the array to have a different mesh subsisted.
+
+   For the *start*: as if it was in position -1, i.e. one "array step" before the first "regular" array copy.
+   For the *end*: as if it was in position *n* + 1, i.e. one "array step" after the last "regular" array copy.
+
+   When *Merge* is activated, and the *cap* vertices are within the *Distance* threshold, they will be merged.
+
+   .. note::
+
+      The start/end cap objects currently do not support the *First Last* option.
+
+
+Hints
+=====
+
+Offset Calculation
+------------------
+
+The transformation applied from one copy to the next is calculated as the sum of the three
+different components (*Relative*, *Constant* and *Object*),
+each of which can be enabled/disabled independently of the others. This allows, for example,
+a relative offset of (1.0, 0.0, 0.0) and a constant offset of (0.1, 0.0, 0.0),
+giving an array of objects neatly spaced along the X axis with a constant 0.1
+unit between them, whatever the original object's size.
+
+
+Examples
+========
+
+.. figure:: /images/modeling_modifiers_generate_array_example-mechanical-chain.png
+
+   A chain created from a single link.
+   `Sample blend-file <https://wiki.blender.org/wiki/File:Dev-ArrayModifier-Chain01.blend>`__.
+
+.. figure:: /images/modeling_modifiers_generate_array_example-organic-tentacle.jpg
+
+   A tentacle created with an Array Modifier followed by a Curve Modifier.
+
+   The segment in the foreground is the base mesh for the tentacle; the tentacle is capped by two
+   specially-modeled objects deformed by the same Curve object as the main part of the tentacle.
+   `Sample blend-file <https://wiki.blender.org/wiki/File:Manual-Modifier-Array-Tentacle01.blend>`__.
+
+
+Fractal
+-------
+
+.. list-table::
+
+   * - .. figure:: /images/modeling_modifiers_generate_array_example-fractal-1.jpg
+          :width: 320px
+
+          Multi-level array animated with motion blur.
+
+     - .. figure:: /images/modeling_modifiers_generate_array_example-fractal-2.png
+          :width: 320px
+
+          Fractal created with multiple arrays.
+          `Sample blend-file <https://wiki.blender.org/wiki/File:Dev-ArrayModifier-Fractal01.blend>`__.

bevel.rst.txt

@@ -0,0 +1,179 @@
+.. _bpy.types.BevelModifier:
+
+**************
+Bevel Modifier
+**************
+
+The *Bevel* modifier bevels the edges of the mesh it is applied to,
+with some control of how and where the bevel is applied to the mesh.
+
+It is a non-destructive alternative to
+the :doc:`Bevel Operation </modeling/meshes/editing/subdividing/bevel>` in Edit Mode.
+
+.. list-table:: Side views of a cube.
+   :align: center
+
+   * - .. figure:: /images/modeling_modifiers_generate_bevel_square-not.png
+          :width: 150px
+
+          Not beveled.
+
+     - .. figure:: /images/modeling_modifiers_generate_bevel_square.png
+          :width: 150px
+
+          Beveled.
+
+
+Options
+=======
+
+.. figure:: /images/modeling_modifiers_generate_bevel_panel.png
+   :align: right
+
+   The Bevel modifier.
+
+Width
+   The size of the bevel effect. See *Width Method* below.
+
+   .. figure:: /images/modeling_modifiers_generate_bevel_cubes.png
+      :width: 350px
+
+      Three Cubes with 0.1, 0.3 and 0.5 bevel widths.
+
+Segments
+   The number of edge loops added along the bevel's face.
+Profile
+   The shape of the bevel, from concave to convex. It has no effect if *Segments* is less than 2.
+Material
+   The index of the material slot to use for the bevel.
+   When set to -1, the material of the nearest original face will be used.
+Only Vertices
+   When enabled, only the areas near vertices are beveled, the edges remain unchanged.
+
+   .. figure:: /images/modeling_modifiers_generate_bevel_cubes-vertices-only.png
+      :width: 350px
+
+      Three cubes with 0.1, 0.3 and 0.5 bevel widths, with *Only Vertices* option enabled.
+
+Clamp Overlap
+   Limits the width of each beveled edge so that edges cannot cause
+   overlapping intersections with other geometry.
+Loop Slide
+   If there are unbeveled edges along with beveled edges into a vertex,
+   the bevel tries to slide along those edges when possible.
+   Turning the option off can lead to more even bevel widths.
+Mark Seams
+   If a seam edge crosses a non-seam one and you bevel all of them,
+   this option will maintain the expected propagation of seams.
+Mark Sharp
+   Similar to Mark Seams, but for sharp edges.
+Harden Normals
+   When enabled, the per-vertex face normals of the bevel faces are adjusted to
+   match the surrounding faces, and the normals of the surrounding faces are not affected.
+   This will keep the surrounding faces flat (if they were before),
+   with the bevel faces shading smoothly into them. For this effect to work,
+   you need custom normals data, which requires *Auto Smooth* option to be enabled
+   (see :doc:`Normals </modeling/meshes/editing/normals>`).
+
+Limit Method
+   Used to control where a bevel is applied to the mesh.
+
+   None
+      No limit, all edges will be beveled.
+   Angle
+      Only edges where the adjacent faces form an angle smaller than the defined threshold will be beveled.
+      Intended to allow you to bevel only the sharp edges of an object without affecting its smooth surfaces.
+   Weight
+      Use each edge's bevel weight to determine the width of the bevel.
+      When the bevel weight is 0.0, no bevel is applied.
+      See :doc:`here </modeling/meshes/editing/edges>` about adjusting bevel weights.
+   Vertex Group
+      Use weights from a vertex group to determine the width of the bevel.
+      When the vertex weight is 0.0, no bevel is applied.
+      An edge is only beveled if both of its vertices are in the vertex group.
+      See :doc:`here </modeling/meshes/properties/vertex_groups/vertex_groups>` about adjusting vertex group weights.
+
+Width Method
+   Declares how *Width* will be interpreted to determine the amount of bevel.
+
+   .. figure:: /images/modeling_modifiers_generate_bevel_width-methods.png
+      :align: right
+      :width: 240
+
+      Width methods.
+
+   Offset
+      Value is interpreted as the distance from the original edge to the edge of the beveled face.
+   Width
+      Value is interpreted as the distance between the two new edges formed by the bevel.
+   Depth
+      Value is the perpendicular distance from the new bevel face to original edge.
+   Percent
+      Similar to *Offset* but the value is interpreted as a percentage of the adjacent edge length.
+
+Set Face Strength Mode
+   Set *Face Strength* on the faces involved in the bevel, according to the mode specified here.
+   This can be used in conjunction with a following
+   :doc:`Weighted Normals </modeling/modifiers/modify/weighted_normal>` modifier
+   (with the *Face Influence* option checked).
+
+   None
+      Do not set face strength.
+   New
+      Set the face strength of new faces along edges to *Medium*,
+      and the face strength of new faces at vertices to *Weak*.
+   Affected
+      In addition to those set for the *New* case,
+      also set the faces adjacent to new faces to have strength *Strong*.
+   All
+      In addition to those set for the *Affected* case,
+      also set all the rest of the faces of the model to have strength *Strong*.
+
+Miter Patterns
+   A *miter* is formed when two beveled edges meet at an angle.
+   On the side where the angle is greater than 180 degrees, if any, it is called an *outer miter*.
+   If it is less than 180 degrees, then it is called an *inner miter*.
+   The outer and inner miters can each be set to one of these patterns:
+
+   Sharp
+      Edges meet at a sharp point, with no extra vertices introduced on the edges.
+   Patch
+      Edges meet at a sharp point but in addition, two extra vertices are introduced near the point
+      so that the edges and faces at the vertex may be less pinched together than
+      what occurs in the *Sharp* case.
+      This pattern does makes no sense for inner miters, so it behaves like *Arc* for them.
+
+      The *Spread* slider controls how far the new vertices are from the meeting point.
+   Arc
+      Two vertices are introduced near the meeting point, and a curved arc joins them together.
+
+      The *Spread* slider controls how far the new vertices are from the meeting point.
+
+      The *Profile* slider controls the shape of the arc.
+
+   .. list-table:: Diagrams of the miter patterns.
+
+      * - .. figure:: /images/modeling_meshes_editing_subdividing_bevel_miter-2.png
+
+             Sharp outer miter.
+
+        - .. figure:: /images/modeling_meshes_editing_subdividing_bevel_miter-3.png
+
+             Patch outer miter.
+
+        - .. figure:: /images/modeling_meshes_editing_subdividing_bevel_miter-4.png
+
+             Arc outer miter.
+
+      * - .. figure:: /images/modeling_meshes_editing_subdividing_bevel_miter-5.png
+
+             Sharp inner miter.
+
+        - .. figure:: /images/modeling_meshes_editing_subdividing_bevel_miter-6.png
+
+             Arc inner miter.
+
+        - ..
+
+Spread
+   The value used to spread extra vertices apart for non-sharp miters.

booleans.rst.txt

@@ -0,0 +1,60 @@
+.. _bpy.types.BooleanModifier:
+
+****************
+Boolean Modifier
+****************
+
+The *Boolean* modifier performs operations on meshes that are otherwise too complex
+to achieve with as few steps by editing meshes manually. It uses one of
+the three available boolean operations to create a single mesh out of two mesh objects:
+
+.. figure:: /images/modeling_modifiers_generate_booleans_union-intersect-difference-examples.png
+
+   The Union, Intersection and Difference between a Cube and a UV Sphere,
+   with the modifier applied to the sphere and using the cube as target.
+
+This modifier needs a second object to be the target (the second operand) of the operation.
+
+.. warning::
+
+   Only :term:`manifold` meshes are guaranteed to give proper results,
+   other cases (especially "opened" meshes, :term:`non-manifold` but without any self-intersections)
+   will usually work well, but might give odd glitches and artifacts in some cases.
+
+   You should also avoid any co-planar faces (or co-linear edges) between both operands,
+   those also tend to give issues currently.
+
+.. tip::
+
+   If you have marked your objects to show the edges
+   (in :menuselection:`Properties Editor --> Object --> Viewport Display`, enable *Wireframe*),
+   you will see the edge creation process while you are moving your objects around. Depending on your mesh topology,
+   you can also enable X-Ray and Transparency and see the topology being created in real-time.
+
+
+Options
+=======
+
+.. figure:: /images/modeling_modifiers_generate_booleans_panel.png
+
+   The Boolean modifier.
+
+
+Operations
+----------
+
+Operation
+   Which boolean operation will be used.
+
+   Difference
+      The target mesh is subtracted from the modified mesh (everything *outside* of the target mesh is kept).
+   Union
+      The target mesh is added to the modified mesh.
+   Intersect
+      Opposite of *Difference* (everything *inside* of the target mesh is kept).
+
+Object
+   The name of the target mesh object.
+
+Overlap Threshold
+   Maximum distance between two faces to consider them as overlapping.

build.rst.txt

@@ -0,0 +1,49 @@
+.. _bpy.types.BuildModifier:
+
+**************
+Build Modifier
+**************
+
+The *Build* modifier causes the faces of the mesh object to appear or disappear one after the other over time.
+
+By default, faces appear in the order in which they are stored in memory (by default, the order of creation).
+The face/vertex order can be altered in Edit Mode by using :ref:`Sort Mesh Elements <mesh-edit-sort-elements>`.
+
+
+Options
+=======
+
+.. figure:: /images/modeling_modifiers_generate_build_panel.png
+   :align: right
+
+   The Build modifier.
+
+Start
+   The start frame of the building process.
+Length
+   The number of frames over which to rebuild the object.
+
+Randomize
+   Randomizes the order in which the faces are built.
+Seed
+   The random seed.
+   Changing this value gives a different "random" order when *Randomize* is checked.
+   This order is always the same for a given seed/mesh set.
+Reversed
+   The modifier will operate in reverse, essentially allowing it to be used as a "deconstruction" effect.
+   This is useful for making a set of dupli-objects gradually disappear.
+
+
+Example
+=======
+
+The *Build* modifier is often useful when needing a way to get a large number of items to progressively appear,
+without resorting to animating the visibility of each one by one.
+Examples of this include a mesh containing vertices only,
+which is used as an :doc:`Instance Verts emitter </scene_layout/object/properties/instancing/verts>`,
+and has the build modifier on it. Such a setup is a workaround/technique for being able to
+art-direct some semi-random layout of a collection of objects (i.e. leaves/balls forming a carpet of sorts)
+when doing so with particles is not desirable
+(e.g. due to undesirable distribution of items leaving random gaps and overlapping in other places).
+
+.. youtube:: -7SqfX5vt_8

decimate.rst.txt

@@ -0,0 +1,116 @@
+.. _bpy.types.DecimateModifier:
+
+*****************
+Decimate Modifier
+*****************
+
+The *Decimate* modifier allows you to reduce the vertex/face count of a mesh with minimal shape changes.
+
+This is not usually used on meshes which have been created by modeling carefully and economically
+(where all vertices and faces are necessary to correctly define the shape).
+But if the mesh is the result of complex modeling,
+sculpting and/or applied :doc:`Subdivision Surface </modeling/modifiers/generate/subdivision_surface>`/
+:doc:`Multiresolution </modeling/modifiers/generate/multiresolution>` modifiers,
+the *Decimate* one can be used to reduce the polygon count for a performance increase,
+or simply remove unnecessary vertices and edges.
+
+Unlike the majority of existing modifiers, this one does not allow
+you to visualize your changes in Edit Mode.
+
+
+Options
+=======
+
+Decimate Type
+-------------
+
+Collapse
+^^^^^^^^
+
+.. figure:: /images/modeling_modifiers_generate_decimate_panel-collapse.png
+   :align: right
+
+   The Decimate modifier in Collapse mode.
+
+Merges vertices together progressively, taking the shape of the mesh into account.
+
+Ratio
+   The ratio of faces to keep after decimation.
+
+   - On 1.0: the mesh is unchanged.
+   - On 0.5: edges have been collapsed such that half the number of faces remain (see note below).
+   - On 0.0: all faces have been removed.
+
+   .. note::
+
+      Although the *Ratio* is directly proportional to the number of remaining faces,
+      triangles are used when calculating the ratio.
+
+      This means that if your mesh contains quads or other polygons,
+      the number of remaining faces will be larger than expected,
+      because those will remain unchanged if their edges are not collapsed.
+
+      This is only true if the *Triangulate* option is disabled.
+
+Vertex Group
+   A vertex group that controls what parts of the mesh are decimated.
+
+   Factor
+      The amount of influence the *Vertex Group* has on the decimation.
+Triangulate
+   Keeps any resulting triangulated geometry from the decimation process.
+Symmetry
+   Maintains symmetry on a single axis.
+
+
+Un-Subdivide
+^^^^^^^^^^^^
+
+.. figure:: /images/modeling_modifiers_generate_decimate_panel-un-subdivide.png
+   :align: right
+
+   The Decimate modifier in Un-Subdivide mode.
+
+It can be thought of as the reverse of subdivide.
+It attempts to remove edges that were the result of a subdivide operation.
+It is intended for meshes with a mainly grid-based topology (without giving uneven geometry).
+If additional editing has been done after the subdivide operation, the results may be unexpected.
+
+Iterations
+   The number of times to perform the un-subdivide operation.
+   Two iterations is the same as one subdivide operation, so you will usually want to use even numbers.
+
+
+Planar
+^^^^^^
+
+.. figure:: /images/modeling_modifiers_generate_decimate_panel-planar.png
+   :align: right
+
+   The Decimate modifier in Planar mode.
+
+It reduces details on forms comprised of mainly flat surfaces.
+
+Angle Limit
+   Dissolve geometry which form angles (between surfaces) higher than this setting.
+
+All Boundaries
+   When enabled, all vertices along the boundaries of faces are dissolved.
+   This can give nicer results when using a high *Angle Limit*.
+
+Delimit
+   Prevent dissolving geometry in certain places.
+
+   Normal
+      Does not dissolve edges on the borders of areas where the face normals are reversed.
+   Material
+      Does not dissolve edges on the borders of where different materials are assigned.
+   Seam
+      Does not dissolve edges marked as seams.
+
+
+Further Options
+---------------
+
+Face Count
+   This label shows the number of remaining faces as a result of applying the *Decimate* modifier.

edge_split.rst.txt

@@ -0,0 +1,76 @@
+.. _bpy.types.EdgeSplitModifier:
+
+*******************
+Edge Split Modifier
+*******************
+
+The *Edge Split* modifier splits, duplicates edges within a mesh,
+breaking 'links' between faces around those split edges.
+
+The edges to split can be determined from the edge angle (i.e. angle between faces forming that edge),
+and/or edges marked as sharp.
+
+Splitting an edge affects vertex normal generation at that edge, making the edge appear sharp.
+Hence, this modifier can be used to achieve the same effect as :ref:`Auto Smooth <auto-smooth>`,
+making edges appear sharp when their angle is above a certain threshold.
+It can also be used for manual control of the smoothing process,
+where the user defines which edges should appear smooth or sharp
+(see :ref:`Mesh Smoothing <modeling-meshes-editing-normals-shading>` for other ways to do this).
+If desired, both modes can be active at once.
+
+.. note::
+
+   This modifier is kept mostly for historical/compatibility reasons.
+   Everything it can do in shading, and much more,
+   can now be achieved using :ref:`custom normals <modeling_meshes_normals_custom>`.
+
+   Unless you really need the topology changes it generates, it is not advised to use it in new projects.
+
+.. note::
+
+   Splitting edges can also be :ref:`performed manually <bpy.ops.mesh.edge_split>` in Edit Mode.
+
+
+Options
+=======
+
+.. figure:: /images/modeling_modifiers_generate_edge-split_panel.png
+   :align: right
+
+   The Edge Split modifier.
+
+Edge Angle
+   When enabled, edges will be split if the angle between its
+   two adjacent faces is greater than the *Split Angle*.
+
+   Split Angle
+      On 0: all edges are split. On 180: no edges are split.
+
+Sharp Edges
+   When enabled, edges will be split if they were :ref:`marked as sharp <bpy.ops.mesh.mark_sharp>`.
+
+.. note::
+
+   :term:`Non-manifold` edges will always be split.
+
+
+Examples
+========
+
+.. list-table::
+
+   * - .. figure:: /images/modeling_modifiers_generate_edge-split_example-1.png
+
+          Flat shading.
+
+     - .. figure:: /images/modeling_modifiers_generate_edge-split_example-2.png
+
+          Smooth shading.
+
+   * - .. figure:: /images/modeling_modifiers_generate_edge-split_example-3.png
+
+          Smooth shading with Edge Split.
+
+     - .. figure:: /images/modeling_modifiers_generate_edge-split_example-4.png
+
+          Smooth shading with Edge Split and Subdivision Surface.

explode.rst.txt

@@ -0,0 +1,79 @@
+.. _bpy.types.ExplodeModifier:
+
+****************
+Explode Modifier
+****************
+
+The *Explode* modifier is used to alter the mesh geometry by moving/rotating its faces in a way
+that roughly tracks particles emitted by that object, making it look as if the mesh is being exploded
+(broken apart and pushed outward).
+
+For this modifier to have any visible effect, there needs to be a particle system on its object.
+That particle system will control how the mesh is exploded.
+
+Both the number of emitted particles and number of faces determine how granular the *Explode* modifier is.
+More faces and more particles will mean more individual pieces.
+
+.. Broken link to the demo video...
+   Here is
+   a `demo video <https://wiki.blender.org/uploads/7/7b/Manual_-_Explode_Modifier_-_Exploding_Cube_-_2.5.ogg>`__
+   showing a cube with a particle system and *Explode* modifier.
+   (`blend-file <https://wiki.blender.org/wiki/File:Manual_-_Explode_Modifier_-_Exploding_Cube_-_2.5.blend>`__).
+
+Here is
+a `demo blend-file <https://wiki.blender.org/wiki/File:Manual_-_Explode_Modifier_-_Exploding_Cube_-_2.5.blend>`__
+showing a cube with a particle system and *Explode* modifier.
+
+.. note::
+
+   The *Explode* modifier must come after the *Particle System* one in the :ref:`modifier stack <modifier-stack>`,
+   in order for the former to get required data from the later.
+
+
+Options
+=======
+
+.. figure:: /images/modeling_modifiers_simulate_explode_panel.png
+   :align: right
+
+   The Explode modifier, with a Particle System above it.
+
+Vertex Group
+   Vertices in this group may not be affected by the *Explode* modifier.
+   Vertices with full weight are not affected at all,
+   while vertices with less weight have a higher chance of being affected.
+
+   Vertices with null weight will be treated like those which do not belong to the group at all, and explode normally.
+
+   Protect
+      Clean vertex group edges. Depending on the weights assigned to that vertex group,
+      either completely protect those faces from being affected by the *Explode* modifier
+      (which would happen if the faces had a weight value of 1),
+      or completely remove protection from those faces
+      (which would happen if the faces had a weight value of 0).
+
+Particle UV
+   If set, the U value of the coordinates in that :term:`UV map` will be overwritten
+   with the age of the particle attached to the matching mesh face
+   (in proportion, from 0 for not yet born particles, to 1 for dead ones).
+
+   The V value is set to a constant 0.5 value.
+
+   This allows e.g. to make the color of a fragment (face) vary during it 'explosion' phase,
+   by using a texture with a gradient of colors along its *U* axis.
+
+Cut Edges
+   Split the mesh in pieces based on location of emitted particles, instead of using existing faces.
+   This will typically give a splitting that appears more random.
+
+Unborn
+   Show faces when their attached particles are unborn.
+Alive
+   Show faces when their attached particles are alive.
+Dead
+   Show faces when their attached particles are dead.
+Size
+   Scale each face using the size of its attached particle, once that particle is alive.
+
+Refresh
+   Refresh data in the *Explode* modifier.

mask.rst.txt

@@ -0,0 +1,46 @@
+.. _bpy.types.MaskModifier:
+
+*************
+Mask Modifier
+*************
+
+The *Mask* modifier allows vertices of an object to be hidden dynamically based on vertex groups.
+
+
+Options
+=======
+
+Mode
+   The Mask Modifier can hide parts of a mesh based on two different modes, selectable from this select menu.
+
+   Vertex Group
+      When the *Vertex Group* option is selected,
+      all vertices belonging to the chosen Vertex Group (with a weight above zero) will be visible,
+      and all other vertices will be hidden.
+
+      .. list-table::
+         The Mask modifier, Vertex Group mode.
+
+         *  - .. figure:: /images/modeling_modifiers_generate_mask_vertex-group.png
+
+            - .. figure:: /images/modeling_modifiers_generate_mask_panel-vertex-group.png
+
+   Armature
+      When in Pose Mode,
+      vertices belonging to the Vertex Group associated with the active bone (same names) will be visible.
+      Vertices not in that group will be hidden.
+
+      .. list-table::
+         The Mask modifier, Armature mode.
+
+         *  - .. figure:: /images/modeling_modifiers_generate_mask_armature.png
+
+            - .. figure:: /images/modeling_modifiers_generate_mask_panel-armature.png
+
+Inverse
+   Normally, vertices belonging to the selected Vertex Group (or group associated with the active pose bone)
+   will be shown. The *Invert* toggle allows you to reverse this behavior, instead only showing vertices
+   which do not belong to the Vertex Group.
+
+Threshold
+   Vertices with weights less or equal to this value will be hidden.

mirror.rst.txt

@@ -0,0 +1,108 @@
+.. _bpy.types.MirrorModifier:
+
+***************
+Mirror Modifier
+***************
+
+The *Mirror* modifier mirrors a mesh along its local X, Y and/or Z axes, across the :term:`Object Origin`.
+It can also use another object as the mirror center, then use that object's local axes instead of its own.
+
+
+Options
+=======
+
+.. figure:: /images/modeling_modifiers_generate_mirror_panel.png
+   :align: right
+
+   The Mirror modifier.
+
+Axis
+   The X, Y, Z axis along which to mirror, i.e. the axis perpendicular to the mirror plane of symmetry.
+
+   To understand how the axis applies to the mirror direction, if you were to mirror on the X axis,
+   the positive X values of the original mesh would become the negative X values on the mirrored side.
+
+   You can select more than one of these axes. And will then get more mirrored copies.
+   With one axis you get a single mirror, with two axes four mirrors, and with all three axes eight mirrors.
+
+Bisect
+   If the mesh is already on both sides of the mirror plane, it is cut by that plane,
+   and only one side (the "negative" one by default) is kept to perform the mirror process.
+
+Flip
+   When *Bisect* is enabled on an axis, you can use this setting to switch the side kept and mirrored
+   (i.e. when it is enabled, the "positive" side will be kept, instead of the "negative" one).
+
+Mirror Object
+   An :ref:`Object Selector <ui-eyedropper>` to select an object (usually an empty),
+   which position and rotation will be used to define mirror planes
+   (instead of using the ones from the modified object).
+
+   You can animate it to animate the mirror effect.
+Vertex Groups
+   Try to mirror existing vertex groups.
+
+   A very nice feature, but one that has very specific prerequisites:
+
+   - The vertex groups you want to mirror must be named following the usual left/right pattern
+     (i.e. suffixed by something like ".R", ".right", ".L", etc.).
+   - The mirror side vertex group must already exist (it will not be created automatically).
+     It must also be completely empty (no vertices assigned to it).
+
+Merge
+   Where a vertex is in the same place (within the *Merge Limit* distance) as its mirror
+   it will be merged with the mirrored vertex.
+Merge Limit
+   The maximum distance between a vertex and its mirror copy at which they are merged together
+   (being snapped on the mirror plane). Needs *Merge* to be enabled.
+
+Clipping
+   Prevents vertices from moving through the mirror plane(s) while the user is transforming them in Edit Mode.
+
+   If it is enabled but vertices are beyond the mirror plane and outside of the *Merge Limit*,
+   the vertices will not be merged. But as soon as the vertices are within *Merge Limit*
+   they are snapped together and cannot be moved beyond the mirror plane.
+
+   .. note::
+
+      Vertices on the mirror plane will be unable to move away from the mirror plane
+      as long as *Clipping* is enabled.
+      You must disable it to be able to move the vertices along the mirror axis again.
+
+Flip UV
+   The *Flip U* and *Flip V* options allows you to mirror the UV texture coordinates across the middle of the image.
+
+   E.g. if you have a vertex with UV coordinates of (0.3, 0.9),
+   its mirror copy will have UV coordinates of (0.7, 0.1).
+
+UV Offsets
+   Amount to shift mirrored UVs on the U/V axes.
+
+   It's useful for baking (as overlapping UVs can cause artifacts to appear in the baked map),
+   so the UVs can be moved outside the image and not used for baking, but still be used for display.
+
+
+Hints
+=====
+
+Many modeling tasks involve creating objects that are symmetrical.
+This modifier offers a simple and efficient way to do this, with real-time update of the mirror as you edit it.
+Once your modeling is completed you can either click *Apply* to make a real version of your mesh,
+or leave it as-is for future editing.
+
+
+Accurately Positioning the Mirror Plane
+---------------------------------------
+
+To apply a *Mirror* modifier, it is common to have to move the object's origin onto
+the edge or face that is to be the axis for mirroring.
+This can be tricky when attempted visually.
+
+A good technique to achieve an exact position is
+to select the edge, then :doc:`snap </scene_layout/object/editing/transform/control/snap>` *Cursor to Selection*.
+This will position the 3D Cursor in the center of the edge.
+Finally, use the :ref:`Set Origin <bpy.ops.object.origin_set>` menu, and select *Origin to 3D Cursor*.
+This will move the object's origin (and thus, the mirror plane) to where the 3D cursor is located,
+and the mirroring will be exact.
+
+An alternative is to use an Empty as a *Mirror Object* that you move to the correct position.

multiresolution.rst.txt

@@ -0,0 +1,93 @@
+..    TODO/Review: {{review|im=needs examples}}.
+
+.. _bpy.types.MultiresModifier:
+
+************************
+Multiresolution Modifier
+************************
+
+The *Multiresolution* modifier (often shortened to "Multires") gives you the ability to subdivide a mesh similarly
+to the :doc:`Subdivision Surface </modeling/modifiers/generate/subdivision_surface>` modifier,
+but also allows you to edit the new subdivision levels in :doc:`Sculpt Mode </sculpt_paint/sculpting/introduction>`.
+
+.. note::
+
+   *Multiresolution* is the only modifier that cannot be repositioned in the stack after any modifier that will
+   change geometry or other object data (i.e. all *Generate*, some *Modify* and some *Simulate* modifiers
+   cannot come before the *Multiresolution* one).
+
+
+Options
+=======
+
+.. figure:: /images/modeling_modifiers_generate_multiresolution_panel.png
+   :align: right
+
+   The Multiresolution modifier.
+
+Type
+   Sets the type of subdivision.
+
+   Simple
+      Maintains the current shape, and simply subdivides edges.
+   Catmull-Clark
+      Creates a smooth surface, usually smaller than the original, using the standard
+      `Catmull-Clark <https://en.wikipedia.org/wiki/Catmull%E2%80%93Clark_subdivision_surface>`__
+      subdivision surface algorithm.
+
+
+Levels
+------
+
+The left column of settings control the general quality generated by the modifier in various contexts.
+
+Preview
+   Set the level of subdivisions to show in Object Mode.
+Sculpt
+   Set the level of subdivisions to use in Sculpt Mode.
+Render
+   Set the level of subdivisions to show when rendering.
+Quality
+   How precisely the vertices are positioned (relatively to their theoretical position),
+   can be lowered to get a better performance when working on heavy meshes.
+
+
+Operations
+----------
+
+The right column gathers several operators necessary to manage multi-resolution workflow.
+
+Subdivide
+   Adds another level of subdivision.
+Delete Higher
+   Deletes all subdivision levels that are higher than the current one.
+Reshape
+   Copies vertex coordinates from another mesh.
+
+   To use it, first select a different mesh object with matching topology and vertex indices,
+   then :kbd:`Shift` select the object you wish to copy vertex coordinates to, and click *Reshape*.
+
+Apply Base
+   Modifies the original unsubdivided mesh to match the form of the subdivided mesh.
+
+
+Further Options
+---------------
+
+UV Smooth
+   How to handle UVs during subdivision.
+
+   Smooth, keep corners
+      UV islands are smoothed, but their boundary remain sharp.
+   Sharp
+      UV remain unchanged.
+
+Subdivide UVs
+   When enabled, the UV maps will also be subdivided.
+   (I.e. Blender will add "virtual" coordinates for all sub-faces created by this modifier.)
+Optimal Display
+   When rendering the wireframe of this object, the wires of the new subdivided edges will be skipped
+   (only displays the edges of the original geometry).
+
+Save External
+   Saves displacements to an external ``.btx`` file.

ocean.rst.txt

@@ -0,0 +1,220 @@
+.. _bpy.types.OceanModifier:
+
+**************
+Ocean Modifier
+**************
+
+The *Ocean* modifier is a tool to simulate and generate a deforming ocean surface,
+and associated texture, used to render the simulation data.
+It is intended to simulate deep ocean waves and foam.
+
+It is a port from the open source `Houdini Ocean Toolkit <https://code.google.com/archive/p/houdini-ocean-toolkit/>`__.
+
+
+Options
+=======
+
+.. figure:: /images/modeling_modifiers_simulate_ocean_panel.png
+   :align: right
+
+   The Ocean modifier.
+
+
+Geometry
+--------
+
+Geometry
+   Generate
+      Creates a tiled mesh grid that exactly corresponds with the resolution of the simulation data.
+
+      When generating a mesh surface, the existing mesh object is completely overridden with the ocean grid.
+      A UV channel is also added, mapping the (0.0 to 1.0) UV space to the simulation grid.
+
+      Repeat X, Repeat Y
+         Controls the number of times the grid is tiled in X and Y directions.
+         UVs for these tiled mesh areas continue outside of the (0.0 to 1.0) UV space.
+
+   Displace
+      Uses the existing geometry rather than replacing it. Vertices are displaced along the local Z axis.
+
+Time
+   The time at which the ocean surface is being evaluated.
+   To make an animated ocean, you will need to :ref:`animate <bpy.ops.anim.keyframe_insert>` this value.
+   The speed that the time value is changing will determine the speed of the wave animation.
+Depth
+   The constant depth of the ocean floor under the simulated area.
+   Lower values simulate shallower waters by producing
+   higher frequency details and smaller waves.
+Random Seed
+   A different :term:`seed` will produce a different simulation result.
+Resolution
+   The main control of quality vs speed in the simulation engine.
+   This determines the resolution of the internal 2D grids generated by the simulation.
+
+   The internal grids are powers of two of the resolution value,
+   so a resolution value of ``16``, will create simulation data of size ``256×256``.
+   The higher the resolution, the more details will be produced, but the slower it will be to calculate.
+
+   .. note::
+
+      When using the *Generate* modifier geometry option,
+      this resolution value also determines the resolution of the generated mesh surface,
+      equal to the resolution of the internal simulation data.
+
+Size
+   A simple scaling factor that does not affect the height of the waves or behavior of the simulation.
+Spatial Size
+   The width of the ocean surface area being simulated, in meters.
+   This also determines the size of the generated mesh, or the displaced area.
+   Of course, you can scale the object with the *Ocean* modifier in Object Mode
+   to tweak the apparent size in your scene.
+
+
+Wave
+----
+
+Choppiness
+   The choppiness of the wave peaks.
+   With a choppiness of 0, the ocean surface is only displaced up and down in the Z direction,
+   but with higher choppiness, the waves are also displaced laterally in X and Y, to create sharper wave peaks.
+Scale
+   An overall scale control for the amplitude of the waves.
+   It approximates the height or depth of the waves above or below zero.
+
+   Rather than just scaling the ocean object in Z, it scales all aspects of the simulation,
+   displacement in X and Y, and corresponding foam and normals too.
+
+Alignment
+   The directionality of the wave shapes due to wind.
+   At a value of 0, the wind and waves are randomly, uniformly oriented.
+
+   With higher *Alignment* values, the wind is blowing in a more constant direction,
+   making the waves appear more compressed and aligned to a single direction.
+
+Direction
+   When using *Alignment*, the direction in degrees that the waves are aligned to (using local X axis as reference).
+Damping
+   When using *Alignment*, this will define the amount that inter-reflected waves are damped out.
+   This has the effect of making the wave motion more directional (not just the wave shape).
+
+   With a *Damping* of 0.0, waves are reflected off each other in every direction, with a *Damping* of 1.0,
+   these inter-reflected waves are damped out, leaving only waves traveling in the direction of the wind.
+
+Smallest Wave
+   A minimum limit for the size of generated waves.
+   Acts similarly to a low-pass filter, removing higher frequency wave detail.
+Wind Velocity
+   Wind speed in meters/second. With a low velocity, waves are restricted to smaller surface waves.
+
+
+Simulation Data Generation Options
+----------------------------------
+
+.. figure:: /images/modeling_modifiers_simulate_ocean_foam-layer-name.png
+   :width: 640px
+   :align: center
+
+   Using foam vertex colors with a named data layer.
+
+By default, the simulator only generates displacement data,
+since it takes the least amount of work and gives the fastest feedback.
+Additional simulation data can be generated for rendering as well.
+
+Generate Normals
+   Simulates additional normal map data.
+
+   This can be used by the Ocean texture, when mapped to Normals,
+   as a bump map, and enables generating normal map image sequences when baking.
+
+Generate Foam
+   Simulates additional foam data.
+
+   This can be retrieved by the Ocean texture for use in texturing (perhaps as a mask),
+   and enables generating foam map image sequences when baking.
+
+   Coverage
+      Tweaks the amount of foam covering the waves, negative values will reduce the amount of foam
+      (leaving only the topmost peaks), positive values will add to it. Typically ranges from (-1.0 to 1.0).
+
+   Foam Data Layer Name
+      Optional name for the vertex data layer,
+      used by the Ocean Modifier to store foam maps as vertex colors.
+      This is required for accessing the foam data in the renderer.
+
+
+Baking
+======
+
+Rather than simulating the ocean data live, it can be baked to files in a given directory.
+When a simulation is baked, the simulator engine is completely bypassed,
+and the modifier/texture retrieves all information from the baked files.
+
+Baking can be advantageous for a few reasons:
+
+- It is faster to use the stored data rather than re-calculating it.
+- It allows rendering of ocean data in external renderers.
+- It enables more advanced foam maps.
+
+
+Data Files
+----------
+
+Simulation data is stored as sequences of ``OpenEXR`` image maps,
+one for each of displacement, normals, and foam (if enabled to be generated).
+Upon loading the data from these baked files, when a frame of the bake sequence is read,
+it is cached in memory. This means that accessing loaded frames subsequent times is fast,
+not incurring the overhead of drive access.
+
+Since these baked files are plain ``OpenEXR``\ 's,
+they can also be opened and rendered in any other application or renderer that supports them.
+
+
+Baking Foam
+-----------
+
+Baking also provides improved foam capabilities. When simulating live,
+the ocean simulator retrieves data for that current frame only. In the case of the foam map,
+this represents the tips of wave crests for that given frame. In reality,
+after foam is created by wave interactions,
+it remains sitting on the top of the wave surface for a while, as it dissipates. With baking,
+it is possible to approximate that behavior, by accumulating foam from previous frames,
+leaving it remaining on the surface.
+
+.. vimeo:: 17517981
+   :width: 500
+   :height: 256
+
+
+Baking Options
+--------------
+
+Start, End
+   Frames of the simulation to bake (inclusive).
+   The start and end frames of the bake are repeated when accessing frames outside of the baked range.
+Cache Path
+   Folder to store the baked EXR files in.
+   The sequences will be in the form ``disp_####.exr``, ``normal_####.exr``,
+   and ``foam_####.exr``, where ``####`` is the four digit frame number.
+   If the cache path folder does not exist, it will be created.
+
+
+Simulation Internals
+====================
+
+The simulator itself uses FFT methods to generate 2D grids of simulation information internally,
+very similar to 2D texture maps.
+The simulator can generate three types of data: displacement, normals,
+and extra data, that is used to calculate wave crest intersections (i.e. foam).
+After simulation, these maps are used to displace the ocean surface geometry in 3D,
+and also can be used for shading via the Ocean texture. The internal simulation engine is
+multi threaded with OpenMP to take advantage of multiple cores.
+
+
+Examples
+========
+
+.. vimeo:: 18911131
+   :width: 500
+   :height: 256
+
+Simulated and baked to image maps in Blender, rendered in 3Delight.

particle_instance.rst.txt

@@ -0,0 +1,194 @@
+.. _bpy.types.ParticleInstanceModifier:
+
+**************************
+Particle Instance Modifier
+**************************
+
+When a *Particle Instance* modifier is added to an object,
+the mesh of this object will be duplicated
+at the location of the particles of the selected *Particle System* from another target object.
+This means that to use this modifier, you must have at least one other object
+that has a :doc:`Particles System </physics/particles/index>` on it.
+
+Because of the correlation in which the *Particle Instance* modifier is
+influenced by the underlying particle systems on other objects, some of the apparent effects
+generated by the modifier can look and act vastly different,
+depending on the underlying settings of the particle systems it is associated with.
+This is worth taking account of, when it seems that the *Particle Instance* modifier settings
+do not return the expected results.
+
+
+Options
+=======
+
+.. figure:: /images/modeling_modifiers_simulate_particle-instance_panel.png
+   :align: right
+
+   The Particle Instance modifier.
+
+Object
+   The target object which has a particle system associated with it.
+Particle System
+   Which particle system from the target *Object* to apply this modifier to.
+
+
+Create From
+-----------
+
+Normal
+   When enabled, the modifier will use the regular (parents) particles
+   to duplicate the mesh of the modified object.
+Children
+   When enabled, the modifier will use the :doc:`children </physics/particles/emitter/children>` particles
+   to duplicate the mesh of the modified object.
+Size
+   Scale the instanced copies of the mesh by the particle size attribute.
+   When this is disabled, all the copies appear the same size as the origin.
+
+   See the particle system's :doc:`Render </physics/particles/emitter/render>`
+   and :doc:`Children </physics/particles/emitter/children>` panels for particle's size options.
+
+
+Show Particles When
+-------------------
+
+Unborn
+   When enabled, the modifier will use the unborn particles
+   to duplicate the mesh of the modified object.
+Alive
+   When enabled, the modifier will use the alive particles
+   to duplicate the mesh of the modified object.
+Dead
+   When enabled, the modifier will use the dead particles
+   to duplicate the mesh of the modified object.
+
+
+Further Options
+---------------
+
+Space
+   World, Local
+      Use :term:`World Space`, or :term:`Local Space` of the target object (that the particle system is assigned to).
+
+      - World space means that the locations of the copies of the modified mesh will depend
+        on the location of the modified object **and** of the target object.
+      - Local space means that the locations of the copies of the modified mesh will depend
+        only on the location of the modified object.
+
+Amount
+   The proportion of particles to be used.
+   Allows you to **randomly** skip particles to adjust the amount of instances.
+
+   .. warning::
+
+      The random algorithm used currently only ensures that relative amount to be respected *statistically*.
+      The actual amount of instances generated will differ from the theoretical one,
+      depending on the *Seed* value of the target particle system (and the *Offset* value described below, too).
+
+      That deviation is not significant with high number of particles,
+      but it will be highly noticeable with low numbers
+      (e.g. with 100 particles in the target system, and an *Amount* value of ``0.1``,
+      it can generate either up to 15 or 5 instances, instead of the 10 expected).
+
+   Offset
+      A relative offset in the range of particles used for instantiation.
+      Allows you to avoid overlapping of the used particles,
+      when the same particle system is used in multiple modifier instances.
+
+      .. tip::
+
+         If you want to fully avoid overlaps, your *Offset* value must be at least as high as your *Amount* value.
+
+Rotation Axis X/Y/Z
+   Specify which axis of the modified object to use as pole axis to apply
+   the rotation from the instantiated particles.
+
+
+Using Paths
+-----------
+
+By default, the instances are placed depending on the particles position in the current frame.
+By enabling this option, you can select the position along the particles path regardless of the current frame.
+
+You can adjust the particles' path (using the *Path* visualization type)
+on the :doc:`Render </physics/particles/emitter/render>` panel of the *Particle System* tab.
+
+.. note::
+
+   The particle system must be :doc:`baked </physics/baking>`, except for *Hair* type or *Keyed* physics.
+
+Create Along Paths
+   This option tries to make the instance of the modified object to follow,
+   to deform its shape along the particle path (or the hair strand).
+Keep Shape
+   Enabling this prevents the instance from being deformed,
+   and places it on the path according to the *Position* value.
+Position
+   Specify what percentage of the path the instance fills,
+   or the position on the path if the *Keep Shape* option is enabled.
+
+   Random
+      Adds some randomness to the *Position* value of each instance.
+
+Rotation
+   Specifies the rotation around the path.
+
+   Random
+      Adds some randomness to the *Rotation* value of each instance.
+
+
+Custom Data Layers
+------------------
+
+These fields allow you to select vertex color layers,
+which will be filled with colors based on the particles information.
+These vertex color layers can be used, for example, in a shader to add variance to a material.
+
+Index Layer
+   A vertex color layer for values based on the particles index.
+Value Layer
+   A vertex color layer for random per-particle values.
+
+
+Examples
+========
+
+.. figure:: /images/modeling_modifiers_simulate_particle-instance_split-plane.jpg
+   :width: 600px
+   :align: center
+
+   Particle Instance modifier example.
+
+The render above shows a single plane mesh object assigned to two different vertex groups
+and each of those vertex groups is assigned to a separate and independent particle system,
+with each particle system being assigned to a different *Particle Instance* modifier.
+In the case shown the *Particle Instance* modifiers are added to a sphere and a cube.
+See `example blend-file
+<https://en.blender.org/uploads/4/48/Manual_-_Modifiers_-_Particle_Instance_Modifiers_-_Split_Plane.blend>`__.
+
+.. figure:: /images/modeling_modifiers_simulate_particle-instance_create-along-paths.jpg
+   :width: 600px
+   :align: center
+
+   Create Along Path example.
+
+In this example, a single *Keyed* particle travels through four points (green planes),
+on an elliptical path. The *Particle Instance* modifier is added to a cylinder object
+and then associated with that *Keyed* particle system.
+
+When the *Create Along Paths* is activated,
+instead of the cylinder location just following the position of the particle,
+the cylinder mesh is fitted to the shape of the path followed by the particle.
+The mesh geometry of the object which is deformed
+can have an impact on how well the deformation is carried out.
+In the case of the cylinder, it has many loop cuts along its length so
+that it can bend at those points to deform along the particle path.
+
+The *Particle Instance* modifier *Create Along Paths* feature works for hair (strand)
+particles as well as with keyed particles. In this case, the mesh of the *Particle Instance* modifier
+will follow the length and profile of the hair strands paths.
+
+.. note::
+
+   Strands, when they are generated, instantly die when created, so for the *Create Along Paths* checkbox
+   to be of any use, you must also have the *Dead* checkbox enabled.

remesh.rst.txt

@@ -0,0 +1,98 @@
+.. _bpy.types.RemeshModifier:
+
+***************
+Remesh Modifier
+***************
+
+The *Remesh* modifier is a tool for generating new mesh topology.
+The output follows the surface curvature of the input, but its topology contains only quads.
+
+
+Options
+=======
+
+.. figure:: /images/modeling_modifiers_generate_remesh_panel.png
+   :align: right
+
+   The Remesh modifier.
+
+Mode
+   There are three basic modes available in the *Remesh* modifier.
+   The output topology is almost identical between the three modes, what changes is the smoothing.
+
+   Blocks
+      There is no smoothing at all.
+   Smooth
+      Output a smooth surface.
+   Sharp
+      Similar to *Smooth*, but preserves sharp edges and corners.
+
+Octree Depth
+   Sets the resolution of the output. Low values will generate larger faces relative to the input,
+   higher values will generate a denser output.
+Scale
+   The result can be tweaked further by this, lower values effectively decrease the output resolution.
+Sharpness
+   Shown when using the *Sharp Mode*. Higher values produce edges more similar to the input,
+   while lower values filter out noise.
+Smooth Shading
+   Output faces with smooth shading rather than flat shading.
+   The smooth/flat shading of the input faces is not preserved.
+Remove Disconnected Pieces
+   Filter out small disconnected pieces of the output.
+
+   Thin parts of the input mesh can become lose, and generate small isolated bits of mesh.
+   This option will remove those.
+
+   Threshold
+      Use this to control how small a disconnected component must be to be removed.
+
+.. note::
+
+   The input mesh should have some thickness to it. If the input is completely flat,
+   add a :doc:`Solidify Modifier </modeling/modifiers/generate/solidify>` above the *Remesh* one.
+
+
+Examples
+========
+
+.. list-table::
+
+   * - .. figure:: /images/modeling_modifiers_generate_remesh_example-none.png
+          :width: 320px
+
+          Unmodified mesh.
+
+     - .. figure:: /images/modeling_modifiers_generate_remesh_example-blocks-depth-3.png
+          :width: 320px
+
+          Blocks mode with Octree Depth 3.
+
+     - .. figure:: /images/modeling_modifiers_generate_remesh_example-smooth-depth-3.png
+          :width: 320px
+
+          Smooth mode with Octree Depth 3.
+
+   * - .. figure:: /images/modeling_modifiers_generate_remesh_example-sharp-depth-2.png
+          :width: 320px
+
+          Sharp mode with Octree Depth 2.
+
+     - .. figure:: /images/modeling_modifiers_generate_remesh_example-sharp-depth-3.png
+          :width: 320px
+
+          Sharp mode with Octree Depth 3.
+
+     - .. figure:: /images/modeling_modifiers_generate_remesh_example-sharp-depth-4.png
+          :width: 320px
+
+          Sharp mode with Octree Depth 4.
+
+.. figure:: /images/modeling_modifiers_generate_remesh_example-text-topology.png
+   :width: 520px
+
+   The Remesh Modifier applied to a text to improve its topology.
+
+.. youtube:: Mh-gUnS2c0Y
+
+.. vimeo:: 21096739

screw.rst.txt

@@ -0,0 +1,61 @@
+.. _bpy.types.ScrewModifier:
+
+**************
+Screw Modifier
+**************
+
+The *Screw* modifier is similar to the :doc:`Screw </modeling/meshes/editing/duplicating/screw>` tool
+in the *Toolbar*, in that it takes a profile object, a mesh or a curve, to create a helix-like shape.
+
+.. figure:: /images/modeling_modifiers_generate_screw_align.png
+   :width: 540px
+
+   Properly aligning the profile object is important.
+
+The profile should be properly aligned to the cardinal direction of the object rather than to the screw axis.
+
+
+Options
+=======
+
+.. figure:: /images/modeling_modifiers_generate_screw_panel.png
+   :align: right
+
+   The Screw modifier.
+
+Axis
+   The axis along which the helix will be built.
+
+   Screw
+      The height of one helix iteration.
+
+Axis Object
+   The name of an object to define the axis direction.
+
+   Object Screw
+      Use the distance from the *Axis Object* to define the height of one helix iteration.
+
+Angle
+   Degrees for a single helix revolution.
+Steps
+   Number of steps used for a single revolution displayed in the 3D View. Beware of setting this higher than
+   *Render Steps*, which is the value used for rendering.
+Render Steps
+   As above, but used during render time. Increase to improve quality.
+Smooth Shading
+   Output faces with smooth shading rather than flat shading.
+   The smooth/flat shading of the input geometry is not preserved.
+Calc Order
+   Order of edges is calculated to avoid problems with normals and shading. Only needed for meshes, not curves.
+Flip
+   Flip normals direction.
+Iterations
+   Number of revolutions.
+Stretch U/V
+   Stretch the UV coordinates from (0.0 to 1.0) when UVs are present.
+Merge Vertices
+   Merge vertices that lie on the axis of rotation.
+   Use this to close off end points with a triangle fan.
+
+   Merge Distance
+      Vertices under this distance to the axis are merged.

skin.rst.txt

@@ -0,0 +1,144 @@
+.. _bpy.types.SkinModifier:
+
+*************
+Skin Modifier
+*************
+
+The *Skin* modifier uses vertices and edges to create a skinned surface,
+using a per-vertex radius to better define the shape.
+The output is mostly quads, although some triangles will appear around intersections.
+
+It is a quick way to generate base meshes for sculpting and/or smooth organic shapes with
+arbitrary topology.
+
+.. note::
+
+   Faces in the original geometry are ignored.
+
+
+Options
+=======
+
+.. figure:: /images/modeling_modifiers_generate_skin_panel.png
+   :align: right
+
+   The Skin modifier.
+
+Branch Smoothing
+   A branch point is a vertex with three or more connected edges.
+   These areas tend to produce more complicated topology, some of which may overlap.
+   This setting relaxes the surface around these points,
+   with the side effect of shrinking it.
+
+Smooth Shading
+   Output faces with smooth shading rather than flat shading.
+   The smooth/flat shading of the input geometry is not preserved.
+
+Symmetry Axes X/Y/Z
+   These checkboxes are used to keep the output topology symmetrical in their respective axes.
+   In other words, using it avoids merging triangles across an axis unless the triangles form a symmetric quad.
+
+   .. note::
+
+      They do not add geometry flipped across an axis.
+      For that, the :doc:`Mirror </modeling/modifiers/generate/mirror>` modifier should be used,
+      typically placed above the *Skin* one.
+
+
+Add Skin Data
+-------------
+
+This modifier uses a :ref:`custom set of data <modeling-modifiers-generate-skin-data>` in the mesh,
+that is generated automatically when you add the modifier the first time.
+
+However, you may remove that data, or loose it some way or the other. That operator will generate it again.
+
+
+Selected Vertices
+-----------------
+
+Those operators modify the original mesh 'control data' for the *Skin* modifier. They help manage its behavior.
+
+Mark/Clear Loose
+   By default, a branch vertex (vertex with three or more connected edges)
+   will generate extra edge loops along adjacent edges in order to keep the output tight.
+   Branches can be made loose by clicking *Mark Loose*, which will allow the output to stretch between
+   all adjacent vertices. This can be disabled again by clicking *Clear Loose*.
+Mark Root
+   Marking a vertex as root causes that vertex to be used for calculating rotations for connected limbs.
+   Root vertices also affect the armature output, they will be used as the origin for the root bones.
+
+   ..
+      Not true anymore:
+      Roots are shown in the *3D View* with a red dashed circle around the vertex.
+
+   Each set of connected vertices should have one root node
+   (one is selected by default if you do not assign any manually).
+   *Mark Root* enforces the one-root per set rule, so it is not necessary to manually unmark roots.
+
+Equalize Radii
+   Makes the skin radii of selected vertices equal on each axis.
+
+
+Create Armature
+---------------
+
+Create an armature on top of the object. Each edge becomes a bone.
+
+.. note::
+
+   If the root vertex has more than one adjacent edge,
+   an extra bone will be created to serve as the root.
+
+This tool does the following:
+
+#. A new armature object is added with bones matching the input mesh.
+   The active selection is switched to the new armature.
+#. Weight groups are added to the input mesh. The *Skin* modifier propagates these weights to the output as well.
+#. An :doc:`Armature </modeling/modifiers/deform/armature>` modifier is added directly below the *Skin* one.
+   Note that the *Armature* modifier is being applied after
+   the *Skin* one because it should only deform the output,
+   whereas if it were above, it might change the resulting topology.
+
+
+.. _modeling-modifiers-generate-skin-data:
+
+Skin Mesh Data
+==============
+
+That modifier needs a set of specific data in the original mesh to work properly.
+This data allows to define the root vertices of each tree, which ones are loose (see `Selected Vertices`_ above),
+and the size (radius) of the skin at each vertex.
+
+
+Skin Size
+---------
+
+The radii of input vertices can be individually scaled in Edit Mode by pressing :kbd:`Ctrl-A`.
+Non-uniform scaling of the X and Y axes is accessible by the usual axis locking with :kbd:`X` or :kbd:`Y`.
+The radius can also be adjusted in the *Transform* panel of the Sidebar, in the 3D View.
+
+
+Examples
+========
+
+.. _fig-modifier-skin-creature:
+
+.. figure:: /images/modeling_modifiers_generate_skin_example.png
+
+   Simple creature, made with only the Skin and Subdivision Surface modifiers.
+
+
+External Links
+==============
+
+- `Skin Modifier Development at Blender Nation
+  <http://www.blendernation.com/2011/03/11/skin-modifier-development/>`__ --
+  An early demonstration of the Skin Modifier by Nicholas Bishop (March 2011).
+- Ji, Zhongping; Liu, Ligang; Wang, Yigang (2010).
+  `B-Mesh: A Fast Modeling System for Base Meshes of 3D Articulated Shapes
+  <http://www.math.zju.edu.cn/ligangliu/CAGD/Projects/BMesh/>`__,
+  Computer Graphics Forum 29(7), pp. 2169-2178. -- The work this modifier is based on
+  (`direct link to PDF <http://www.math.zju.edu.cn/ligangliu/cagd/projects/bmesh/paper/bmesh.pdf>`__).
+- `Related thread on Blender artists
+  <http://blenderartists.org/forum/showthread.php?209551-B-mesh-modeling-tools-papers-better-than-zsfere>`__.

solidify.rst.txt

@@ -0,0 +1,110 @@
+.. _bpy.types.SolidifyModifier:
+
+*****************
+Solidify Modifier
+*****************
+
+The *Solidify* modifier takes the surface of any mesh and adds depth, thickness to it.
+
+
+Options
+=======
+
+.. figure:: /images/modeling_modifiers_generate_solidify_panel.png
+   :align: right
+
+   The Solidify modifier.
+
+Thickness
+   The depth to be solidified.
+Offset
+   A value between (-1 to 1) to locate the solidified output inside or outside the original mesh.
+   Set to 0.0, the solidified output will be centered on the original mesh.
+Clamp
+   A value between (0 to 2) to clamp offsets to avoid self-intersection.
+
+   .. figure:: /images/modeling_modifiers_generate_solidify_clamp.png
+
+      Clamp Offset.
+
+Vertex Group
+   Only vertices in this group are solidified. Their weights are multiplied by the thickness,
+   so vertices with lower weights will be less thick.
+
+   Invert
+      Reverses the vertex group, so that only vertices which are **not** in the vertex group are solidified.
+   Factor
+      How much the vertex weights are taken into account.
+
+      - On 0.0 , vertices with zero weight will have no thickness at all.
+      - On 0.5 , vertices with zero weight will be half as thick as those with full weight.
+      - On 1.0 , the weights are ignored and the *Thickness* value is used for every vertex.
+
+Crease
+   These options are intended for usage with
+   the :doc:`Subdivision Surface </modeling/modifiers/generate/subdivision_surface>` modifier.
+
+   .. figure:: /images/modeling_modifiers_generate_solidify_rims.png
+      :width: 350px
+
+      Rim and edges. In this example, the object was assigned a second material used to color the rim red.
+
+   Inner
+      Set a crease to the inner edges.
+   Outer
+      Set a crease to the outer edges.
+   Rim
+      Set a crease to the rim.
+
+Flip Normals
+   Reverse the normals of all geometry (both the inner and outer surfaces).
+Even Thickness
+   Maintain thickness by adjusting for sharp corners.
+   Sometimes improves quality but also increases computation time.
+High Quality Normals
+   Normals are calculated to produce a more even thickness.
+   Sometimes improves quality but also increases computation time.
+Fill Rim
+   Fills the gap between the inner and outer edges.
+Only Rim
+   Will not extrude surfaces parallel to the original one, but instead will only generate the perpendicular rim.
+
+.. note::
+
+   *Fill Rim* and *Only Rim* only make a difference on :term:`non-manifold` objects,
+   since the rims are generated from the borders of the original geometry.
+
+Material Index Offset
+   Choose a different material to use for the new geometry.
+   This is applied as an offset from the original material of the face from which it was solidified.
+
+   - A value of 0 means it will use the same material.
+   - A value of 1 means it will use the material immediately below the original material.
+   - A value of -2 means the material two positions above the original material will be used.
+
+   These are clamped to the top-most and bottom-most material slots.
+
+   Rim
+      Similarly, you can give another material to the rim faces.
+
+.. important::
+
+   The modifier thickness is calculated using local vertex coordinates. If the object has non-uniform scale,
+   the thickness will vary on different sides of the object.
+
+   To fix this, either :ref:`apply <bpy.ops.object.transform_apply>`
+   or :ref:`clear <bpy.ops.object.*clear>` the scale.
+
+
+Known Limitations
+=================
+
+Even Thickness
+--------------
+
+Solidify thickness is an approximation.
+While *Even Thickness* and *High Quality Normals* should yield good results,
+the final wall thickness is not guaranteed and may vary depending on the mesh topology.
+
+In order to maintain precise wall thickness in every case, we would need to add/remove faces on the offset shell,
+something this modifier does not do since this would add a lot of complexity and slow it down.

subdivision_surface.rst.txt

@@ -0,0 +1,184 @@
+.. _bpy.types.SubsurfModifier:
+
+****************************
+Subdivision Surface Modifier
+****************************
+
+The *Subdivision Surface* modifier (often shorten to "Subdiv")
+is used to split the faces of a mesh into smaller faces, giving it a smooth appearance.
+It enables you to create complex smooth surfaces while modeling simple, low-vertex meshes.
+It avoids the need to save and maintain huge amounts of data,
+and gives a smooth "organic" look to the object.
+
+As with any modifier, order of execution (position in the :ref:`modifier stack <modifier-stack>`)
+has an important bearing on the results.
+
+Keep in mind that this is a different operation than its companion,
+:ref:`Smooth Shading <modeling-meshes-editing-normals-shading>`.
+You can see the difference between the two in the grid image below.
+
+.. figure:: /images/modeling_modifiers_generate_subdivision-surface_grid.png
+
+   Subdivision levels 0 to 3, without and with Smooth Shading.
+
+.. tip::
+
+   The *Subdivision Surface* modifier does not allow you to edit the new subdivided geometry without applying it,
+   but the :doc:`Multiresolution </modeling/modifiers/generate/multiresolution>` modifier does (in Sculpt Mode).
+
+.. note::
+
+   This modifier now uses
+   the `OpenSubdiv library <http://graphics.pixar.com/opensubdiv/docs/intro.html>`__ as a backend.
+
+
+Options
+=======
+
+.. figure:: /images/modeling_modifiers_generate_subdivision-surface_panel.png
+   :align: right
+
+   The Subdivision Surface modifier.
+
+Type
+   This toggle button allows you to choose the subdivision algorithm:
+
+   Catmull-Clark
+      The default option, subdivides and smooths the surfaces.
+      According to its `Wikipedia page <https://en.wikipedia.org/wiki/Catmull%E2%80%93Clark_subdivision_surface>`__,
+      the "arbitrary-looking formula was chosen by Catmull and Clark based on the aesthetic appearance of
+      the resulting surfaces rather than on a mathematical derivation."
+   Simple
+      Only subdivides the surfaces, without any smoothing
+      (the same as the :ref:`Subdivide <bpy.ops.mesh.subdivide>` operator, in Edit Mode).
+      Can be used, for example, to increase base mesh resolution when using displacement maps.
+
+Subdivisions
+   Recursively adds more geometry.
+
+   The right combination of these settings will allow you to keep a fast and lightweight approximation of your model
+   when interacting with it in the 3D Viewport, but use a higher quality version when rendering.
+
+   .. warning::
+
+      Higher levels of subdivisions results in more vertices, which means more memory will be occupied
+      (both system RAM, and video memory for display).
+      Blender could potentially crash or hang if you do not have enough available memory.
+
+   Render
+      The number of subdivision levels shown in renders.
+   Viewport
+      The number of subdivision levels shown in the 3D View.
+   Quality
+      How precisely the vertices are positioned
+      (relatively to their theoretical position of an infinitely subdivided mesh),
+      can be lowered to get a better performance.
+
+      Using higher values does not necessarily mean real improvement in quality,
+      ideal results might be reached well before the maximum *Quality* value.
+
+   .. tip::
+
+      Be careful not to set the *Viewport* subdivisions higher than the *Render* subdivisions,
+      this would mean that in the 3D View the quality will be higher than the rendered.
+
+Options
+   UV Smooth
+      How to handle UVs during subdivision.
+
+      Smooth, keep corners
+         UV islands are smoothed, but their boundary remain sharp.
+      Sharp
+         UV remain unchanged.
+
+   Optimal Display
+      When rendering the wireframe of this object, the wires of the new subdivided edges will be skipped
+      (only displays the edges of the original geometry).
+
+   Use Creases
+      Use the `Weighted Edge Creases`_ values stored in edges to control how smooth they are made.
+
+
+Keyboard Shortcuts
+==================
+
+To quickly add a *Subdivision Surface* modifier to one or more objects, select the object(s) and press :kbd:`Ctrl-1`.
+That will add a Subdivision Surface modifier with *Viewport* subdivisions set to 1.
+You can use other numbers too, such as :kbd:`Ctrl-2`, :kbd:`Ctrl-3`, etc,
+to add a modifier with that number of subdivisions.
+Adding a *Subdivision Surface* modifier in this fashion will not modify the *Render* subdivisions.
+
+If an object already has a *Subdivision Surface* modifier,
+doing this will simply change its subdivision level instead of adding another modifier.
+
+
+Control
+=======
+
+Catmull-Clark subdivision rounds off edges, and often this is not what you want.
+There are several solutions that allow you to control the subdivision.
+
+
+.. _modifiers-generate-subsurf-creases:
+
+Weighted Edge Creases
+---------------------
+
+Weighted edge creases for subdivision surfaces allows you to change the way
+the *Subdivision Surface* modifier subdivides the geometry to give the edges a smooth or sharp appearance.
+
+.. figure:: /images/modeling_modifiers_generate_subdivision-surface_withcrease.png
+
+   A subdivided cube with creased edges.
+
+The crease weight of selected edges can be changed in the *Transform* panel, Sidebar of the 3D View.
+The scale-like dedicated tool :kbd:`Shift-E` can also be used to adjust the crease weight.
+A higher value makes the edge "stronger" and more resistant to the smoothing effect of subdivision surfaces.
+
+
+Edge Loops
+----------
+
+.. figure:: /images/modeling_modifiers_generate_subdivision-surface_cube-with-edge-loops.png
+
+   Subdivision Level 2 cube, the same with an extra Edge Loop, and the same with six extra Edge Loops.
+
+The *Subdivision Surface* modifier demonstrates why good, clean topology is so important.
+As you can see in the figure, the it has a drastic effect on a default cube.
+Until you add in additional loops (with e.g. :ref:`Loop Cut and Slide <bpy.ops.mesh.loopcut_slide>`),
+the shape is almost unrecognizable as a cube.
+
+A mesh with deliberate topology has good placement of edge loops, which allow the placement of more loops
+(or their removal) to control the sharpness/smoothness of the resultant mesh.
+
+
+Known Limitations
+=================
+
+Non-Contiguous Normals
+----------------------
+
+Blender's subdivision system produces nice smooth subdivided meshes, but any subdivided face
+(that is, any small face created by the algorithm from a single face of the original mesh),
+shares the overall normal orientation of that original face.
+
+.. list-table::
+
+   * - .. figure:: /images/modeling_modifiers_generate_subdivision-surface_normal-orientation-1.png
+          :width: 320px
+
+          Comparison of good normals and bad normals.
+
+     - .. figure:: /images/modeling_modifiers_generate_subdivision-surface_normal-orientation-2.png
+          :width: 320px
+
+          Side view of image on the left.
+
+Abrupt normal changes can produce ugly black gouges even though
+these flipped normals are not an issue for the shape itself.
+
+A quick way to fix this is to use Blender's
+:doc:`Recalculate Normals </modeling/meshes/editing/normals>` operation in Edit Mode.
+
+If you still have some ugly black gouges you will have to
+:doc:`manually flip the normals </modeling/meshes/editing/normals>`.

triangulate.rst.txt

@@ -0,0 +1,55 @@
+.. _bpy.types.TriangulateModifier:
+
+********************
+Triangulate Modifier
+********************
+
+The *Triangulate* modifier converts all faces in a mesh (quads and polygons) to triangular faces.
+It fulfills the exact same function as the :ref:`Triangulate <bpy.ops.mesh.quads_convert_to_tris>` tool in Edit Mode.
+
+.. list-table::
+
+   * - .. figure:: /images/modeling_modifiers_generate_triangulate_before.png
+          :width: 320px
+
+          Mesh before Triangulate modifier.
+
+     - .. figure:: /images/modeling_modifiers_generate_triangulate_after.png
+          :width: 320px
+
+          Mesh after Triangulate modifier.
+
+
+Options
+=======
+
+.. figure:: /images/modeling_modifiers_generate_triangulate_panel.png
+   :align: right
+
+   The Triangulate modifier.
+
+Quad Method
+   Beauty
+      Split the quads in nice triangles, slower method.
+   Fixed
+      Split the quads on their 1st and 3rd vertices.
+   Fixed Alternate
+      Split the quads on their 2nd and 4th vertices.
+   Shortest Diagonal
+      Split the quads based on the diagonal distance between their vertices.
+
+N-gon Method
+   Beauty
+      Arrange the new triangles nicely, slower method.
+   Clip
+      Split the polygons using an ear-clipping algorithm
+      (gives similar results to the tessellation used for the viewport rendering).
+
+Keep Normals
+   When using :ref:`custom normals <modeling_meshes_normals_custom>`,
+   try to preserve the same shading as before triangulation.
+
+Minimum Vertices
+   Minimum number of vertices a face must have to be triangulated.
+   For example, setting this value to 5, will prevent triangulation of :term:`quads <quad>`
+   and only triangulate :term:`N-gons <N-gon>`.

wireframe.rst.txt

@@ -0,0 +1,86 @@
+.. _bpy.types.WireframeModifier:
+
+******************
+Wireframe Modifier
+******************
+
+The *Wireframe* modifier transforms a mesh into a wireframe by iterating over its
+faces, collecting all edges and turning those edges into four sided polygons.
+Be aware of the fact that your mesh needs to have faces to be wireframed.
+You can define the thickness, the material and several other parameters of the generated
+wireframe dynamically via the given modifier options.
+
+
+Options
+=======
+
+.. figure:: /images/modeling_modifiers_generate_wireframe_panel.png
+   :align: right
+
+   The Wireframe modifier.
+
+Thickness
+   The depth or size of the wireframes.
+Offset
+   A value between (-1 to 1) to change whether the wireframes are
+   generated inside or outside of the original mesh.
+   Set to zero, *Offset* will center the wireframes around the original edges.
+Vertex Group
+   Restrict the modifier to only this vertex group.
+
+   Invert
+      Inverts the vertex group weights.
+   Factor
+      Percentage that the vertex has influence over the final wireframe result.
+
+Crease Edges
+   This option is intended for usage with
+   the :doc:`Subdivision </modeling/modifiers/generate/subdivision_surface>` modifier.
+   Enable this option to crease edges on their junctions and prevent large curved intersections.
+
+   Crease Weight
+      Define how much crease (0 to 1, nothing to full) the junctions should receive.
+
+Even Thickness
+   Maintain thickness by adjusting for sharp corners. Sometimes improves quality but also increases computation time.
+Relative Thickness
+   Determines the edge thickness by the length of the edge. Longer edges will be thicker.
+Boundary
+   Creates wireframes on mesh island boundaries.
+Replace Original
+   If this option is enabled, the original mesh is replaced by the generated wireframe.
+   If not, the wireframe is generated on top of it.
+Material Offset
+   Uses the chosen material index as the material for the wireframe;
+   this is applied as an offset from the first material.
+
+.. warning::
+
+   Wireframe thickness is an approximation. While *Even Thickness* should yield good results in many cases,
+   skinny faces can cause ugly spikes. In this case you can either reduce the extreme angles in the geometry
+   or disable the *Even Thickness* option.
+
+
+Examples
+========
+
+.. figure:: /images/modeling_modifiers_generate_wireframe_result.jpg
+   :width: 420px
+
+   Wireframes on a displaced plane.
+
+In this example, the wireframes carry a second (dark) material while the displaced plane uses its original one.
+
+.. figure:: /images/modeling_modifiers_generate_wireframe_example-weights.png
+   :width: 420px
+
+   Vertex Group weighting.
+
+The weights of the vertex group gradually change from 0 to 1.
+
+.. figure:: /images/modeling_modifiers_generate_wireframe_example-crease.png
+   :width: 420px
+
+   Wireframe and Subdivision Surface modifier.
+
+Cube with enabled *Crease Edges* option. The *Crease Weight* is set to 0, 0.5 and 1.