When the parameters and handles for an operator are being defined by the VEX code, disable the Create New buttons on the Parameters and Handles pages of the Type Properties dialog.

When the parameters and handles for an operator are being defined by the VEX code, disable the Create New buttons on the Parameters and Handles pages of the Type Properties dialog.

When the parameters and handles for an operator are being defined by the VEX code, disable the Create New buttons on the Parameters and Handles pages of the Type Properties dialog.

When the parameters and handles for an operator are being defined by the VEX code, disable the Create New buttons on the Parameters and Handles pages of the Type Properties dialog.

Fixed bug where composite operations may have used incorrect bounds and extend (hold) conditions when the alpha bounds did not match the color bounds.

Fixed bug where composite operations may have used incorrect bounds and extend (hold) conditions when the alpha bounds did not match the color bounds.

Fixed bug where composite operations may have used incorrect bounds and extend (hold) conditions when the alpha bounds did not match the color bounds.

Fixed bug where composite operations may have used incorrect bounds and extend (hold) conditions when the alpha bounds did not match the color bounds.

Fixed bug where composite operations may have used incorrect bounds and extend (hold) conditions when the alpha bounds did not match the color bounds.

The Expand COP is now faster and more easily interruptable. The non-high quality mode's image quality has been improved enough that it can be used for almost all expansions now.

The Expand COP is now faster and more easily interruptable. The non-high quality mode's image quality has been improved enough that it can be used for almost all expansions now.

The Expand COP is now faster and more easily interruptable. The non-high quality mode's image quality has been improved enough that it can be used for almost all expansions now.

The Expand COP is now faster and more easily interruptable. The non-high quality mode's image quality has been improved enough that it can be used for almost all expansions now.

The Expand COP is now faster and more easily interruptable. The non-high quality mode's image quality has been improved enough that it can be used for almost all expansions now.

Added new dilate/erode COP which performs a more efficient, though not as nice version of the expand COPs expand/shrink operations.

Added new dilate/erode COP which performs a more efficient, though not as nice version of the expand COPs expand/shrink operations.

Added new dilate/erode COP which performs a more efficient, though not as nice version of the expand COPs expand/shrink operations.

Added new dilate/erode COP which performs a more efficient, though not as nice version of the expand COPs expand/shrink operations.

Added new dilate/erode COP which performs a more efficient, though not as nice version of the expand COPs expand/shrink operations.

In most places in Houdini where we look for the "pscale" attribute, we now look for a single float value which represents uniform scale (previous behaviour) or a 3-float value named "scale" which represents scale in X, Y and Z. This allows non-uniform scale when instancing, stamping, copying, etc.

In the POP context, there are now three new local variables:

• $SCALEX: The first component of the 3-float pscale attribute
• $SCALEY: The second component of the 3-float pscale attribute
• $SCALEZ: The third component of the 3-float pscale attribute

The existing $PSCALE attribute still refers to the uniform scale.

The two forms work in conjunction with each other. That is, if there are two attributes named "pscale" and an attribute named "scale", the scales will be cumulative (i.e. multiplied together) to form the final scale.

In most places in Houdini where we look for the "pscale" attribute, we now look for a single float value which represents uniform scale (previous behaviour) or a 3-float value named "scale" which represents scale in X, Y and Z. This allows non-uniform scale when instancing, stamping, copying, etc.

In the POP context, there are now three new local variables:

• $SCALEX: The first component of the 3-float pscale attribute
• $SCALEY: The second component of the 3-float pscale attribute
• $SCALEZ: The third component of the 3-float pscale attribute

The existing $PSCALE attribute still refers to the uniform scale.

The two forms work in conjunction with each other. That is, if there are two attributes named "pscale" and an attribute named "scale", the scales will be cumulative (i.e. multiplied together) to form the final scale.

In most places in Houdini where we look for the "pscale" attribute, we now look for a single float value which represents uniform scale (previous behaviour) or a 3-float value named "scale" which represents scale in X, Y and Z. This allows non-uniform scale when instancing, stamping, copying, etc.

In the POP context, there are now three new local variables:

• $SCALEX: The first component of the 3-float pscale attribute
• $SCALEY: The second component of the 3-float pscale attribute
• $SCALEZ: The third component of the 3-float pscale attribute

The existing $PSCALE attribute still refers to the uniform scale.

The two forms work in conjunction with each other. That is, if there are two attributes named "pscale" and an attribute named "scale", the scales will be cumulative (i.e. multiplied together) to form the final scale.

In most places in Houdini where we look for the "pscale" attribute, we now look for a single float value which represents uniform scale (previous behaviour) or a 3-float value named "scale" which represents scale in X, Y and Z. This allows non-uniform scale when instancing, stamping, copying, etc.

In the POP context, there are now three new local variables:

• $SCALEX: The first component of the 3-float pscale attribute
• $SCALEY: The second component of the 3-float pscale attribute
• $SCALEZ: The third component of the 3-float pscale attribute

The existing $PSCALE attribute still refers to the uniform scale.

The two forms work in conjunction with each other. That is, if there are two attributes named "pscale" and an attribute named "scale", the scales will be cumulative (i.e. multiplied together) to form the final scale.

In most places in Houdini where we look for the "pscale" attribute, we now look for a single float value which represents uniform scale (previous behaviour) or a 3-float value named "scale" which represents scale in X, Y and Z. This allows non-uniform scale when instancing, stamping, copying, etc.

In the POP context, there are now three new local variables:

• $SCALEX: The first component of the 3-float pscale attribute
• $SCALEY: The second component of the 3-float pscale attribute
• $SCALEZ: The third component of the 3-float pscale attribute

The existing $PSCALE attribute still refers to the uniform scale.

The two forms work in conjunction with each other. That is, if there are two attributes named "pscale" and an attribute named "scale", the scales will be cumulative (i.e. multiplied together) to form the final scale.

It is now possible to create VOPNETs as networks within networks.