The Brush SOPs now use a seperate UV radius from the 3d Radius. This is because the UV scales are usually quiet different from the 3d scales, and ideally one is moving the brush between the two viewports.

The Brush SOPs now use a seperate UV radius from the 3d Radius. This is because the UV scales are usually quiet different from the 3d scales, and ideally one is moving the brush between the two viewports.

The Brush SOPs now use a seperate UV radius from the 3d Radius. This is because the UV scales are usually quiet different from the 3d scales, and ideally one is moving the brush between the two viewports.

The Brush SOPs now use a seperate UV radius from the 3d Radius. This is because the UV scales are usually quiet different from the 3d scales, and ideally one is moving the brush between the two viewports.

Trying to carve or loft polygons with zero vertices will no longer lead to possible crashes.

Trying to carve or loft polygons with zero vertices will no longer lead to possible crashes.

Trying to carve or loft polygons with zero vertices will no longer lead to possible crashes.

Trying to carve or loft polygons with zero vertices will no longer lead to possible crashes.

Trying to carve or loft polygons with zero vertices will no longer lead to possible crashes.

There were some problems when applying displacement bounds to certain primitive types (curve, point and mesh primitives notably). This caused the displacement bounds to be incorrect for these primitives, potentially generating artifacts in the output image.

There were some problems when applying displacement bounds to certain primitive types (curve, point and mesh primitives notably). This caused the displacement bounds to be incorrect for these primitives, potentially generating artifacts in the output image.

There were some problems when applying displacement bounds to certain primitive types (curve, point and mesh primitives notably). This caused the displacement bounds to be incorrect for these primitives, potentially generating artifacts in the output image.

There were some problems when applying displacement bounds to certain primitive types (curve, point and mesh primitives notably). This caused the displacement bounds to be incorrect for these primitives, potentially generating artifacts in the output image.

There were some problems when applying displacement bounds to certain primitive types (curve, point and mesh primitives notably). This caused the displacement bounds to be incorrect for these primitives, potentially generating artifacts in the output image.

The Basis SOP has a new menu option to re-parameterize the curves according to the arc length.

The Basis SOP has a new menu option to re-parameterize the curves according to the arc length.

The Basis SOP has a new menu option to re-parameterize the curves according to the arc length.

The Basis SOP has a new menu option to re-parameterize the curves according to the arc length.

The Basis SOP has a new menu option to re-parameterize the curves according to the arc length.

A new dropdown menu allows to select the type of parameterization of the path (if the object is positioned on any). The default, arc length choice will interpret the position parameter, as the fraction of the total path length, and position the object there. The uniform option will use the position parameter as the domain parameter of the curve (the old behaviour).

Also, the handle, when set to 1.0 and dragged back a bit, will correctly set the parameter to the value above 0.9 but less than 1.0. Previously the paramter was being set to the value greater than 1.9.

A new dropdown menu allows to select the type of parameterization of the path (if the object is positioned on any). The default, arc length choice will interpret the position parameter, as the fraction of the total path length, and position the object there. The uniform option will use the position parameter as the domain parameter of the curve (the old behaviour).

Also, the handle, when set to 1.0 and dragged back a bit, will correctly set the parameter to the value above 0.9 but less than 1.0. Previously the paramter was being set to the value greater than 1.9.

A new dropdown menu allows to select the type of parameterization of the path (if the object is positioned on any). The default, arc length choice will interpret the position parameter, as the fraction of the total path length, and position the object there. The uniform option will use the position parameter as the domain parameter of the curve (the old behaviour).

Also, the handle, when set to 1.0 and dragged back a bit, will correctly set the parameter to the value above 0.9 but less than 1.0. Previously the paramter was being set to the value greater than 1.9.

A new dropdown menu allows to select the type of parameterization of the path (if the object is positioned on any). The default, arc length choice will interpret the position parameter, as the fraction of the total path length, and position the object there. The uniform option will use the position parameter as the domain parameter of the curve (the old behaviour).

Also, the handle, when set to 1.0 and dragged back a bit, will correctly set the parameter to the value above 0.9 but less than 1.0. Previously the paramter was being set to the value greater than 1.9.

A new dropdown menu allows to select the type of parameterization of the path (if the object is positioned on any). The default, arc length choice will interpret the position parameter, as the fraction of the total path length, and position the object there. The uniform option will use the position parameter as the domain parameter of the curve (the old behaviour).

Also, the handle, when set to 1.0 and dragged back a bit, will correctly set the parameter to the value above 0.9 but less than 1.0. Previously the paramter was being set to the value greater than 1.9.

Added a new option to the helpbrowser command to display the help for a particular operator type.