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.

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

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

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

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

When generating .i3d files using motion blur, there were bugs computing bounding boxes when the velocity was negative. This has been addressed.

When generating .i3d files using motion blur, there were bugs computing bounding boxes when the velocity was negative. This has been addressed.

When generating .i3d files using motion blur, there were bugs computing bounding boxes when the velocity was negative. This has been addressed.

When generating .i3d files using motion blur, there were bugs computing bounding boxes when the velocity was negative. This has been addressed.

When generating .i3d files using motion blur, there were bugs computing bounding boxes when the velocity was negative. This has been addressed.

The -i option to hscript forces hscript to use a simpler method of reading input. The alfred output driver uses this option to work-around the non-standard way that alfred sends input to hscript.

The -i option to hscript forces hscript to use a simpler method of reading input. The alfred output driver uses this option to work-around the non-standard way that alfred sends input to hscript.

The -i option to hscript forces hscript to use a simpler method of reading input. The alfred output driver uses this option to work-around the non-standard way that alfred sends input to hscript.

The -i option to hscript forces hscript to use a simpler method of reading input. The alfred output driver uses this option to work-around the non-standard way that alfred sends input to hscript.

The -i option to hscript forces hscript to use a simpler method of reading input. The alfred output driver uses this option to work-around the non-standard way that alfred sends input to hscript.

There is a new function (getbounds()) which will return the bounding box of geometry from a disk file.

There is a new function (getbounds()) which will return the bounding box of geometry from a disk file.