This COP2 cache now works properly with cache sizes over 4 gigabytes on systems that support this.

This COP2 cache now works properly with cache sizes over 4 gigabytes on systems that support this.

This COP2 cache now works properly with cache sizes over 4 gigabytes on systems that support this.

Optimized the premultiply COP for the 8 and 16 bit cases. Performance has improved from 2-4x.

Optimized the premultiply COP for the 8 and 16 bit cases. Performance has improved from 2-4x.

Optimized the premultiply COP for the 8 and 16 bit cases. Performance has improved from 2-4x.

Optimized the premultiply COP for the 8 and 16 bit cases. Performance has improved from 2-4x.

Optimized the premultiply COP for the 8 and 16 bit cases. Performance has improved from 2-4x.

The Edit VEX Function button available on VEX operators (such as the Gradient COP or Mountain SOP) now brings up a Type Properties dialog if the operator is defined in an OTL. Otherwise it still tries to locate the VEX source code on disk and open a text editor on that file.

The Edit VEX Function button available on VEX operators (such as the Gradient COP or Mountain SOP) now brings up a Type Properties dialog if the operator is defined in an OTL. Otherwise it still tries to locate the VEX source code on disk and open a text editor on that file.

The Edit VEX Function button available on VEX operators (such as the Gradient COP or Mountain SOP) now brings up a Type Properties dialog if the operator is defined in an OTL. Otherwise it still tries to locate the VEX source code on disk and open a text editor on that file.

The Edit VEX Function button available on VEX operators (such as the Gradient COP or Mountain SOP) now brings up a Type Properties dialog if the operator is defined in an OTL. Otherwise it still tries to locate the VEX source code on disk and open a text editor on that file.

The Edit VEX Function button available on VEX operators (such as the Gradient COP or Mountain SOP) now brings up a Type Properties dialog if the operator is defined in an OTL. Otherwise it still tries to locate the VEX source code on disk and open a text editor on that file.

Fixed a bug with some RenderMan SHOPs incorrectly reporting their shader names in the Type Properties dialog. The shader name would appear as "opdef:/Shop/ri_constant" for example, where the correct value would be "constant".

Fixed a bug with some RenderMan SHOPs incorrectly reporting their shader names in the Type Properties dialog. The shader name would appear as "opdef:/Shop/ri_constant" for example, where the correct value would be "constant".

Fixed a bug with some RenderMan SHOPs incorrectly reporting their shader names in the Type Properties dialog. The shader name would appear as "opdef:/Shop/ri_constant" for example, where the correct value would be "constant".

Fixed a bug with some RenderMan SHOPs incorrectly reporting their shader names in the Type Properties dialog. The shader name would appear as "opdef:/Shop/ri_constant" for example, where the correct value would be "constant".

Fixed a bug with some RenderMan SHOPs incorrectly reporting their shader names in the Type Properties dialog. The shader name would appear as "opdef:/Shop/ri_constant" for example, where the correct value would be "constant".

When doing a File->New operation, or when loading a new hip file, persistent handle groups were not being destroyed. Now they are.

When doing a File->New operation, or when loading a new hip file, persistent handle groups were not being destroyed. Now they are.

When doing a File->New operation, or when loading a new hip file, persistent handle groups were not being destroyed. Now they are.

When doing a File->New operation, or when loading a new hip file, persistent handle groups were not being destroyed. Now they are.

When doing a File->New operation, or when loading a new hip file, persistent handle groups were not being destroyed. Now they are.

The Edit Contents dialog would sometimes erroneously report that a section had been changed even when it had not been changed. This problem would occur under Windows because of carriage return characters not being handled properly.

The Edit Contents dialog would sometimes erroneously report that a section had been changed even when it had not been changed. This problem would occur under Windows because of carriage return characters not being handled properly.