If you specify a global variable name or a VCC reserved word as the Parameter Name in a Parameter VOP, the Parameter VOP now gets an error flag which says that an invalid Parameter Name has been specified. Previously, specifying a Global Variable name would result in the Parameter Name automatically changing itself. Setting it to a VCC reserved word would result in compiler warnings or errors.

If you specify a global variable name or a VCC reserved word as the Parameter Name in a Parameter VOP, the Parameter VOP now gets an error flag which says that an invalid Parameter Name has been specified. Previously, specifying a Global Variable name would result in the Parameter Name automatically changing itself. Setting it to a VCC reserved word would result in compiler warnings or errors.

If you specify a global variable name or a VCC reserved word as the Parameter Name in a Parameter VOP, the Parameter VOP now gets an error flag which says that an invalid Parameter Name has been specified. Previously, specifying a Global Variable name would result in the Parameter Name automatically changing itself. Setting it to a VCC reserved word would result in compiler warnings or errors.

If "$signature" was used in the code block of a script based VOP, it was not being expanded properly. It would always expand to the parameter value of the signature parameter, instead of the real signature being used, which could be affected by the data types of connected inputs. This bug is now fixed.

If "$signature" was used in the code block of a script based VOP, it was not being expanded properly. It would always expand to the parameter value of the signature parameter, instead of the real signature being used, which could be affected by the data types of connected inputs. This bug is now fixed.

If "$signature" was used in the code block of a script based VOP, it was not being expanded properly. It would always expand to the parameter value of the signature parameter, instead of the real signature being used, which could be affected by the data types of connected inputs. This bug is now fixed.

If "$signature" was used in the code block of a script based VOP, it was not being expanded properly. It would always expand to the parameter value of the signature parameter, instead of the real signature being used, which could be affected by the data types of connected inputs. This bug is now fixed.

If "$signature" was used in the code block of a script based VOP, it was not being expanded properly. It would always expand to the parameter value of the signature parameter, instead of the real signature being used, which could be affected by the data types of connected inputs. This bug is now fixed.

VOP Parameters are now animatable. However, as they always evaluate at time 0, a warning is generated if a time dependent expression is used. The purpose of this change is to allow constant expressions like "$PI" or "1/3" to be used.

VOP Parameters are now animatable. However, as they always evaluate at time 0, a warning is generated if a time dependent expression is used. The purpose of this change is to allow constant expressions like "$PI" or "1/3" to be used.

VOP Parameters are now animatable. However, as they always evaluate at time 0, a warning is generated if a time dependent expression is used. The purpose of this change is to allow constant expressions like "$PI" or "1/3" to be used.

VOP Parameters are now animatable. However, as they always evaluate at time 0, a warning is generated if a time dependent expression is used. The purpose of this change is to allow constant expressions like "$PI" or "1/3" to be used.

VOP Parameters are now animatable. However, as they always evaluate at time 0, a warning is generated if a time dependent expression is used. The purpose of this change is to allow constant expressions like "$PI" or "1/3" to be used.

The default saving method has been changed to "Numbered Backups"

The default saving method has been changed to "Numbered Backups"

The default saving method has been changed to "Numbered Backups"

The default saving method has been changed to "Numbered Backups"

The default saving method has been changed to "Numbered Backups"

When generating velocity based motion blur IFD's, Houdini will now generate smaller .ifd files for mantra. The velocity blur is now done in mantra rather than in Houdini. This also means that velocity motion blur works if the object is set to render from disk files (instead of Houdini passing down the geometry).

When generating velocity based motion blur IFD's, Houdini will now generate smaller .ifd files for mantra. The velocity blur is now done in mantra rather than in Houdini. This also means that velocity motion blur works if the object is set to render from disk files (instead of Houdini passing down the geometry).