The Box SOP has a Polygon Mesh type which is similar to the Mesh option but generates Polygons suitable for further poly operations.

The Box SOP has a Polygon Mesh type which is similar to the Mesh option but generates Polygons suitable for further poly operations.

The Box SOP has a Polygon Mesh type which is similar to the Mesh option but generates Polygons suitable for further poly operations.

The Box SOP has a Polygon Mesh type which is similar to the Mesh option but generates Polygons suitable for further poly operations.

New SOP: The TransformAxis. This allows you to have animatable parameters to translate, scale, and rotate around a specified axis.

New SOP: The TransformAxis. This allows you to have animatable parameters to translate, scale, and rotate around a specified axis.

New SOP: The TransformAxis. This allows you to have animatable parameters to translate, scale, and rotate around a specified axis.

New SOP: The TransformAxis. This allows you to have animatable parameters to translate, scale, and rotate around a specified axis.

New SOP: The TransformAxis. This allows you to have animatable parameters to translate, scale, and rotate around a specified axis.

After doing a proximity capture in the Capture Geometry state, you can now use the middle-mouse button in the viewport to adjust your drop-off.

After doing a proximity capture in the Capture Geometry state, you can now use the middle-mouse button in the viewport to adjust your drop-off.

After doing a proximity capture in the Capture Geometry state, you can now use the middle-mouse button in the viewport to adjust your drop-off.

After doing a proximity capture in the Capture Geometry state, you can now use the middle-mouse button in the viewport to adjust your drop-off.

After doing a proximity capture in the Capture Geometry state, you can now use the middle-mouse button in the viewport to adjust your drop-off.

The omls command now takes an optional "-t optype" parameter like all the other om commands. This command now lists only those manipulators that can be bound to the specified op type (defaults to Sop).

The omls command now takes an optional "-t optype" parameter like all the other om commands. This command now lists only those manipulators that can be bound to the specified op type (defaults to Sop).

The omls command now takes an optional "-t optype" parameter like all the other om commands. This command now lists only those manipulators that can be bound to the specified op type (defaults to Sop).

The omls command now takes an optional "-t optype" parameter like all the other om commands. This command now lists only those manipulators that can be bound to the specified op type (defaults to Sop).

The omls command now takes an optional "-t optype" parameter like all the other om commands. This command now lists only those manipulators that can be bound to the specified op type (defaults to Sop).

The ombind command now prevents the user from creating bindings between a manipulator meant for manipulating one type of op, and an op of another type. For example, the transform2d manipulator only works on cop2 nodes. Previously this rule was not enforced in any way. Now it is.

The ombind command now prevents the user from creating bindings between a manipulator meant for manipulating one type of op, and an op of another type. For example, the transform2d manipulator only works on cop2 nodes. Previously this rule was not enforced in any way. Now it is.

The ombind command now prevents the user from creating bindings between a manipulator meant for manipulating one type of op, and an op of another type. For example, the transform2d manipulator only works on cop2 nodes. Previously this rule was not enforced in any way. Now it is.

The ombind command now prevents the user from creating bindings between a manipulator meant for manipulating one type of op, and an op of another type. For example, the transform2d manipulator only works on cop2 nodes. Previously this rule was not enforced in any way. Now it is.

The ombind command now prevents the user from creating bindings between a manipulator meant for manipulating one type of op, and an op of another type. For example, the transform2d manipulator only works on cop2 nodes. Previously this rule was not enforced in any way. Now it is.

It is now possible to put non-bone objects into IK bone chains and the IK solver will still generate correct solutions. There will be problems in some situations (such as non-uniform scales and lookat constraints). But now there is a lot more flexibility in allowable bone chain setups.