diff options
Diffstat (limited to 'doc/python_api/rst/bge_types/bge.types.BL_ArmatureChannel.rst')
| -rw-r--r-- | doc/python_api/rst/bge_types/bge.types.BL_ArmatureChannel.rst | 28 |
1 files changed, 14 insertions, 14 deletions
diff --git a/doc/python_api/rst/bge_types/bge.types.BL_ArmatureChannel.rst b/doc/python_api/rst/bge_types/bge.types.BL_ArmatureChannel.rst index d8fcfa8cbe4..0ce89ba46e8 100644 --- a/doc/python_api/rst/bge_types/bge.types.BL_ArmatureChannel.rst +++ b/doc/python_api/rst/bge_types/bge.types.BL_ArmatureChannel.rst @@ -88,11 +88,11 @@ base class --- :class:`PyObjectPlus` :type: vector [X, Y, Z]. .. note:: - + You can only move a bone if it is unconnected to its parent. An action playing on the armature may change the value. An IK chain does not update this value, see joint_rotation. .. note:: - + Changing this field has no immediate effect, the pose is updated when the armature is updated during the graphic render (see :data:`BL_ArmatureObject.update`). .. attribute:: scale @@ -102,11 +102,11 @@ base class --- :class:`PyObjectPlus` :type: vector [sizeX, sizeY, sizeZ]. .. note:: - + An action playing on the armature may change the value. An IK chain does not update this value, see joint_rotation. .. note:: - + Changing this field has no immediate effect, the pose is updated when the armature is updated during the graphic render (see :data:`BL_ArmatureObject.update`) .. attribute:: rotation_quaternion @@ -116,11 +116,11 @@ base class --- :class:`PyObjectPlus` :type: vector [qr, qi, qj, qk]. .. note:: - + This field is only used if rotation_mode is 0. An action playing on the armature may change the value. An IK chain does not update this value, see joint_rotation. .. note:: - + Changing this field has no immediate effect, the pose is updated when the armature is updated during the graphic render (see :data:`BL_ArmatureObject.update`) .. attribute:: rotation_euler @@ -130,11 +130,11 @@ base class --- :class:`PyObjectPlus` :type: vector [X, Y, Z]. .. note:: - + This field is only used if rotation_mode is > 0. You must always pass the angles in [X, Y, Z] order; the order of applying the angles to the bone depends on rotation_mode. An action playing on the armature may change this field. An IK chain does not update this value, see joint_rotation. .. note:: - + Changing this field has no immediate effect, the pose is updated when the armature is updated during the graphic render (see :data:`BL_ArmatureObject.update`) .. attribute:: rotation_mode @@ -152,7 +152,7 @@ base class --- :class:`PyObjectPlus` .. attribute:: pose_matrix - pose matrix in armature space, read-only, + pose matrix in armature space, read-only, This field is updated after the graphic render, it represents the current pose. :type: matrix [4][4] @@ -257,19 +257,19 @@ base class --- :class:`PyObjectPlus` * 3DoF joint X+Y+Z: treated as a revolute joint. The [x, y, z] vector represents the equivalent rotation vector to bring the joint from the rest pose to the new pose. :type: vector [x, y, z] - + .. note:: - + The bone must be part of an IK chain if you want to set the ik_dof_x/ik_dof_y/ik_dof_z attributes via the UI, but this will interfere with this attribute since the IK solver will overwrite the pose. You can stay in control of the armature if you create an IK constraint but do not finalize it (e.g. don't set a target) the IK solver will not run but the IK panel will show up on the UI for each bone in the chain. .. note:: - + [0, 0, 0] always corresponds to the rest pose. .. note:: - + You must request the armature pose to update and wait for the next graphic frame to see the effect of setting this attribute (see :data:`BL_ArmatureObject.update`). .. note:: - + You can read the result of the calculation in rotation or euler_rotation attributes after setting this attribute. |