Fixed bug where the 'v' key in the groups channel lister would also attempt to paste keys if you have the dopesheet opened.

Fixed bug where the 'v' key in the groups channel lister would also attempt to paste keys if you have the dopesheet opened.

Fixed bug where the 'v' key in the groups channel lister would also attempt to paste keys if you have the dopesheet opened.

Fixed bug where the 'v' key in the groups channel lister would also attempt to paste keys if you have the dopesheet opened.

Fixed bug where the 'v' key in the groups channel lister would also attempt to paste keys if you have the dopesheet opened.

Metaball generation for RIB is now improved. Due to a mis-interpretation of the metaball OP codes described in Application note #31, we were previously incorrectly generating scales on metaballs based on their weight. The RIB standard does not seem to support a generalized weight per metaball and thus, the weight of each metaball is silently ignored in RIB generation making RIB files smaller. The one exception is that if the weight of the metaball being output is less than 0, the metaball is subtracted from the sum of all other metaballs.

Metaball generation for RIB is now improved. Due to a mis-interpretation of the metaball OP codes described in Application note #31, we were previously incorrectly generating scales on metaballs based on their weight. The RIB standard does not seem to support a generalized weight per metaball and thus, the weight of each metaball is silently ignored in RIB generation making RIB files smaller. The one exception is that if the weight of the metaball being output is less than 0, the metaball is subtracted from the sum of all other metaballs.

Metaball generation for RIB is now improved. Due to a mis-interpretation of the metaball OP codes described in Application note #31, we were previously incorrectly generating scales on metaballs based on their weight. The RIB standard does not seem to support a generalized weight per metaball and thus, the weight of each metaball is silently ignored in RIB generation making RIB files smaller. The one exception is that if the weight of the metaball being output is less than 0, the metaball is subtracted from the sum of all other metaballs.

Metaball generation for RIB is now improved. Due to a mis-interpretation of the metaball OP codes described in Application note #31, we were previously incorrectly generating scales on metaballs based on their weight. The RIB standard does not seem to support a generalized weight per metaball and thus, the weight of each metaball is silently ignored in RIB generation making RIB files smaller. The one exception is that if the weight of the metaball being output is less than 0, the metaball is subtracted from the sum of all other metaballs.

Metaball generation for RIB is now improved. Due to a mis-interpretation of the metaball OP codes described in Application note #31, we were previously incorrectly generating scales on metaballs based on their weight. The RIB standard does not seem to support a generalized weight per metaball and thus, the weight of each metaball is silently ignored in RIB generation making RIB files smaller. The one exception is that if the weight of the metaball being output is less than 0, the metaball is subtracted from the sum of all other metaballs.

There are two additional metaball kernel types available now. The "Hart" kernel, suggested by John Hart which was previously shipped as a plug-in (via proto_install) has now been added to the base library. The other kernel is the kernel used by Pixar's Renderman (and possibly other RIB renderers), which is defined as: Density = 1 - 3*R^2 + 3*R^4 - R^6 As a note, to generate similar results to RenderMan/Entropy, set the metaball weight to 2.5 (or -2.5).

There are two additional metaball kernel types available now. The "Hart" kernel, suggested by John Hart which was previously shipped as a plug-in (via proto_install) has now been added to the base library. The other kernel is the kernel used by Pixar's Renderman (and possibly other RIB renderers), which is defined as: Density = 1 - 3*R^2 + 3*R^4 - R^6 As a note, to generate similar results to RenderMan/Entropy, set the metaball weight to 2.5 (or -2.5).

There are two additional metaball kernel types available now. The "Hart" kernel, suggested by John Hart which was previously shipped as a plug-in (via proto_install) has now been added to the base library. The other kernel is the kernel used by Pixar's Renderman (and possibly other RIB renderers), which is defined as: Density = 1 - 3*R^2 + 3*R^4 - R^6 As a note, to generate similar results to RenderMan/Entropy, set the metaball weight to 2.5 (or -2.5).

There are two additional metaball kernel types available now. The "Hart" kernel, suggested by John Hart which was previously shipped as a plug-in (via proto_install) has now been added to the base library. The other kernel is the kernel used by Pixar's Renderman (and possibly other RIB renderers), which is defined as: Density = 1 - 3*R^2 + 3*R^4 - R^6 As a note, to generate similar results to RenderMan/Entropy, set the metaball weight to 2.5 (or -2.5).

There are two additional metaball kernel types available now. The "Hart" kernel, suggested by John Hart which was previously shipped as a plug-in (via proto_install) has now been added to the base library. The other kernel is the kernel used by Pixar's Renderman (and possibly other RIB renderers), which is defined as: Density = 1 - 3*R^2 + 3*R^4 - R^6 As a note, to generate similar results to RenderMan/Entropy, set the metaball weight to 2.5 (or -2.5).

If HOUDINI_BACKUP_DIR is set to an invalid directory, we now reset it to the current directory and tell the user.

If HOUDINI_BACKUP_DIR is set to an invalid directory, we now reset it to the current directory and tell the user.

If HOUDINI_BACKUP_DIR is set to an invalid directory, we now reset it to the current directory and tell the user.

If HOUDINI_BACKUP_DIR is set to an invalid directory, we now reset it to the current directory and tell the user.

If HOUDINI_BACKUP_DIR is set to an invalid directory, we now reset it to the current directory and tell the user.

The Compositor now has snapping and a new Snap Options dialog. All position handles (Rotospline points, transforms, ramp handles, etc) have the current snap settings applied to them. Snapping can optionally be done against:

• 10 user-defined guides in U or V
• a user-defined grid
• the edges of the image.