[Bf-docboard-svn] bf-manual: [8653] trunk/blender_docs/manual: Merge branch 'blender-3.0-release'
Alaska
noreply at blender.org
Mon Nov 22 02:02:38 CET 2021
Revision: 8653
https://developer.blender.org/rBM8653
Author: Alaska
Date: 2021-11-22 02:02:37 +0100 (Mon, 22 Nov 2021)
Log Message:
-----------
Merge branch 'blender-3.0-release'
Modified Paths:
--------------
trunk/blender_docs/manual/advanced/command_line/render.rst
trunk/blender_docs/manual/editors/preferences/system.rst
trunk/blender_docs/manual/getting_started/installing/linux.rst
trunk/blender_docs/manual/grease_pencil/modes/draw/tools/draw.rst
trunk/blender_docs/manual/grease_pencil/modes/draw/tools/erase.rst
trunk/blender_docs/manual/modeling/geometry_nodes/attribute/capture_attribute.rst
trunk/blender_docs/manual/modeling/geometry_nodes/attributes_reference.rst
trunk/blender_docs/manual/modeling/geometry_nodes/fields.rst
trunk/blender_docs/manual/modeling/geometry_nodes/geometry/transform.rst
trunk/blender_docs/manual/modeling/geometry_nodes/inspection.rst
trunk/blender_docs/manual/modeling/geometry_nodes/instances/rotate_instances.rst
trunk/blender_docs/manual/modeling/geometry_nodes/instances/scale_instances.rst
trunk/blender_docs/manual/modeling/geometry_nodes/instances/translate_instances.rst
trunk/blender_docs/manual/modeling/geometry_nodes/instances.rst
trunk/blender_docs/manual/render/cycles/gpu_rendering.rst
trunk/blender_docs/manual/render/cycles/render_settings/sampling.rst
trunk/blender_docs/manual/render/layers/passes.rst
trunk/blender_docs/manual/video_editing/sequencer/sidebar/strip.rst
trunk/blender_docs/manual/video_editing/sequencer/strips/introduction.rst
Property Changed:
----------------
trunk/blender_docs/
Index: trunk/blender_docs
===================================================================
--- trunk/blender_docs 2021-11-22 01:00:26 UTC (rev 8652)
+++ trunk/blender_docs 2021-11-22 01:02:37 UTC (rev 8653)
Property changes on: trunk/blender_docs
___________________________________________________________________
Modified: svn:mergeinfo
## -1,3 +1,3 ##
/branches/blender-2.92-release/blender_docs:7610-7921
/branches/blender-2.93-release/blender_docs:7959-8113
-/branches/blender-3.0-release/blender_docs:8543-8649
\ No newline at end of property
+/branches/blender-3.0-release/blender_docs:8543-8652
\ No newline at end of property
Modified: trunk/blender_docs/manual/advanced/command_line/render.rst
===================================================================
--- trunk/blender_docs/manual/advanced/command_line/render.rst 2021-11-22 01:00:26 UTC (rev 8652)
+++ trunk/blender_docs/manual/advanced/command_line/render.rst 2021-11-22 01:02:37 UTC (rev 8653)
@@ -110,8 +110,8 @@
``--cycles-device CPU``
Override the device that is used to render frames.
- Currently supported options are ``CPU``, ``CUDA``, and ``OPTIX``.
- Additionally, you can use ``OPTIX+CPU`` in order to use both CPU and GPU rendering.
+ Currently supported options are ``CPU``, ``CUDA``, ``OPTIX``, and ``HIP``.
+ Additionally, you can append ``+CPU`` to any GPU type for hybrid rendering.
``--cycles-print-stats``
Show detailed statistics about memory and time usage for Cycles renders on the console.
Modified: trunk/blender_docs/manual/editors/preferences/system.rst
===================================================================
--- trunk/blender_docs/manual/editors/preferences/system.rst 2021-11-22 01:00:26 UTC (rev 8652)
+++ trunk/blender_docs/manual/editors/preferences/system.rst 2021-11-22 01:02:37 UTC (rev 8653)
@@ -27,9 +27,11 @@
When set to *None* or when the only option is *None*:
the CPU will be used as the computing device for Cycles.
CUDA
- If the system has a compatible Nvidia CUDA device, it will show up an option for rendering with Cycles.
+ If the system has a compatible Nvidia CUDA device, it will show up as an option for rendering with Cycles.
OptiX
- If the system has a compatible Nvidia OptiX device, it will show up an option for rendering with Cycles.
+ If the system has a compatible Nvidia OptiX device, it will show up as an option for rendering with Cycles.
+HIP
+ If the system has a compatible AMD HIP device, it will show up as an option for rendering with Cycles.
.. _prefs-system-cycles-distributive-memory:
Modified: trunk/blender_docs/manual/getting_started/installing/linux.rst
===================================================================
--- trunk/blender_docs/manual/getting_started/installing/linux.rst 2021-11-22 01:00:26 UTC (rev 8652)
+++ trunk/blender_docs/manual/getting_started/installing/linux.rst 2021-11-22 01:02:37 UTC (rev 8653)
@@ -32,8 +32,8 @@
and may provide other features (given by the package manager),
such as listing of packages, update notifications and automatic menu configuration.
Be aware, though, that the package may be outdated compared to the latest official release,
-or not include some features of Blender.
-For example, some distributions do not build Blender with CUDA support, for licensing reasons.
+or not include some features of Blender. For example, some distributions do not build Blender with
+Cycles GPU rendering support, for licensing or other reasons.
If there is a specific package for your distribution, you may choose what is preferable and most convenient,
otherwise, the official binary is available on `blender.org <https://www.blender.org/download/>`__.
Modified: trunk/blender_docs/manual/grease_pencil/modes/draw/tools/draw.rst
===================================================================
--- trunk/blender_docs/manual/grease_pencil/modes/draw/tools/draw.rst 2021-11-22 01:00:26 UTC (rev 8652)
+++ trunk/blender_docs/manual/grease_pencil/modes/draw/tools/draw.rst 2021-11-22 01:02:37 UTC (rev 8653)
@@ -143,7 +143,6 @@
Adds randomness to the position of the points along the stroke.
You can toggle the use of Randomize using the checkbox in the section panel header.
-
.. _bpy.types.BrushGpencilSettings.use_stroke_random_radius:
.. _bpy.types.BrushGpencilSettings.use_random_press_radius:
.. _bpy.types.BrushGpencilSettings.random:
Modified: trunk/blender_docs/manual/grease_pencil/modes/draw/tools/erase.rst
===================================================================
--- trunk/blender_docs/manual/grease_pencil/modes/draw/tools/erase.rst 2021-11-22 01:00:26 UTC (rev 8652)
+++ trunk/blender_docs/manual/grease_pencil/modes/draw/tools/erase.rst 2021-11-22 01:02:37 UTC (rev 8653)
@@ -29,7 +29,7 @@
.. _bpy.types.BrushGpencilSettings.use_default_eraser:
Default Eraser
- Use this brush when enabling the eraser tool with fast switch key (:kbd:`Ctrl`).
+ Use this brush when enabling the eraser tool with the fast switch key (:kbd:`Ctrl`).
.. _bpy.types.BrushGpencilSettings.eraser_mode:
Modified: trunk/blender_docs/manual/modeling/geometry_nodes/attribute/capture_attribute.rst
===================================================================
--- trunk/blender_docs/manual/modeling/geometry_nodes/attribute/capture_attribute.rst 2021-11-22 01:00:26 UTC (rev 8652)
+++ trunk/blender_docs/manual/modeling/geometry_nodes/attribute/capture_attribute.rst 2021-11-22 01:02:37 UTC (rev 8653)
@@ -25,8 +25,8 @@
.. note::
Because this node stores an :ref:`anonymous attribute <anonymous-attributes>` in the geometry,
- it's essential use the geometry output for further operations in the node tree. The anonymous
- attribute will not exist for any other geometry besides the output.
+ it's essential to use the geometry output for further operations in the node tree.
+ The anonymous attribute will not exist for any other geometry besides the output.
Inputs
@@ -60,10 +60,10 @@
.. figure:: /images/modeling_geometry-nodes_attribute_capture-attribute_example.png
-Here, a noise texture is evaluated in along the path of the curve in 1 dimension
-and rendered with a shader. The capture node is essential because the output of
-the :doc:`/modeling/geometry_nodes/curve/curve_to_mesh` does not have "Curve Parameter",
-since it is a mesh and not a curve. So the :doc:`/modeling/geometry_nodes/curve/curve_parameter`
+Here, a noise texture is evaluated in along the path of the curve in one dimension
+and rendered with a shader. The capture node is required because the output of
+the :doc:`/modeling/geometry_nodes/curve/curve_to_mesh` does not have a "curve parameter",
+since it is a mesh and not a curve. So, the :doc:`/modeling/geometry_nodes/curve/curve_parameter`
must be evaluated while the geometry is still a curve.
Internally, after the noise texture is evaluated on the curve,
Modified: trunk/blender_docs/manual/modeling/geometry_nodes/attributes_reference.rst
===================================================================
--- trunk/blender_docs/manual/modeling/geometry_nodes/attributes_reference.rst 2021-11-22 01:00:26 UTC (rev 8652)
+++ trunk/blender_docs/manual/modeling/geometry_nodes/attributes_reference.rst 2021-11-22 01:02:37 UTC (rev 8653)
@@ -30,6 +30,7 @@
To the left of the menu, the attribute domain is shown followed by the attribute name.
To the right of the menu, the attribute data type is shown.
+
.. _anonymous-attributes:
Anonymous Attributes
@@ -42,7 +43,6 @@
which refer to an attribute stored on a geometry.
An anonymous attribute is a set of generic data stored on a geometry that doesn't have a name.
-
Usually, attributes exposed in Blender's interface all have names. However,
in geometry nodes, attributes can be passed around with node sockets.
In these cases, an *Attribute Field* output is created, which is used by
@@ -51,9 +51,8 @@
Anonymous attributes are still stored on the geometry like other attributes, and they are even
automatically interpolated when the geometry changes with other nodes, except for a few cases.
So generally, if the node link is still accessible, the attribute it references will be too.
-
However, anonymous attributes cannot be connected to a completely separate geometry
-that was not created from their source. To transfer attributes between separate geometries,
+that was not created from their source. To transfer attributes between separate pieces of geometry,
the :doc:`/modeling/geometry_nodes/attribute/transfer_attribute` can be used.
Modified: trunk/blender_docs/manual/modeling/geometry_nodes/fields.rst
===================================================================
--- trunk/blender_docs/manual/modeling/geometry_nodes/fields.rst 2021-11-22 01:00:26 UTC (rev 8652)
+++ trunk/blender_docs/manual/modeling/geometry_nodes/fields.rst 2021-11-22 01:02:37 UTC (rev 8653)
@@ -9,19 +9,15 @@
A field input to a node.
-
-What Are Fields?
-================
-
Fundamentally, a field is a function: a set of instructions that can transform an arbitrary number
-of inputs into a single output. A field's result can then be calculated many times with different
-input data. They are used all over geometry nodes to allow calculations that have different results
+of inputs into a single output. A field's result can then be calculated many times with different input data.
+They are used all over geometry nodes to allow calculations that have different results
for every element (mesh vertices, faces, etc.).
For example, in the figure above, the field connected to the "Set Position" node
-depends on two inputs, :doc:`position </modeling/geometry_nodes/input/position>` and
+depends on two inputs, :doc:`position </modeling/geometry_nodes/input/position>` and
:doc:`index </modeling/geometry_nodes/input/index>`, and transforms them into
-into a vector using a single instruction.
+a vector using a single instruction.
Field Visualization
@@ -28,7 +24,7 @@
===================
Socket shapes are used to convey which sockets are fields and which regular data.
-There are three possible socket shapes, each conveying the socket's "field status":
+There are three possible socket shapes, each visualizing its "field status":
:Circle:
The socket requires a single real value, it cannot accept a field input.
@@ -47,12 +43,12 @@
:align: center
@@ Diff output truncated at 10240 characters. @@
More information about the Bf-docboard-svn
mailing list