Fixed potential core dump when using the opparm -c command with an invalid parameter name specified.

Fixed potential core dump when using the opparm -c command with an invalid parameter name specified.

Fixed potential core dump when using the opparm -c command with an invalid parameter name specified.

Fixed potential core dump when using the opparm -c command with an invalid parameter name specified.

Fixed the signatures of the Add Attribute VOP so that the adata input has the correct data type and the localvar input is always of type string.

Fixed the signatures of the Add Attribute VOP so that the adata input has the correct data type and the localvar input is always of type string.

Fixed the signatures of the Add Attribute VOP so that the adata input has the correct data type and the localvar input is always of type string.

Fixed the signatures of the Add Attribute VOP so that the adata input has the correct data type and the localvar input is always of type string.

Fixed the signatures of the Add Attribute VOP so that the adata input has the correct data type and the localvar input is always of type string.

In the Type Properties Dialog for a VOP operator, it is now possible to edit the label for the default signature. It is also possible to swap the default signature with the one next to it using the left arrow button in the column header. Previously both of these operations would do nothing.

In the Type Properties Dialog for a VOP operator, it is now possible to edit the label for the default signature. It is also possible to swap the default signature with the one next to it using the left arrow button in the column header. Previously both of these operations would do nothing.

In the Type Properties Dialog for a VOP operator, it is now possible to edit the label for the default signature. It is also possible to swap the default signature with the one next to it using the left arrow button in the column header. Previously both of these operations would do nothing.

In the Type Properties Dialog for a VOP operator, it is now possible to edit the label for the default signature. It is also possible to swap the default signature with the one next to it using the left arrow button in the column header. Previously both of these operations would do nothing.

In the Type Properties Dialog for a VOP operator, it is now possible to edit the label for the default signature. It is also possible to swap the default signature with the one next to it using the left arrow button in the column header. Previously both of these operations would do nothing.

When using SHOPs defined in OTLs or using the Render From File option on an object, or using a texture map where the file is embedded in an operator definition in an OTL, the data is no longer embedded in the .ifd file. Instead, mantra is now capable of reading files using the opdef: syntax. The exception to this is if the operator type definition is part of the Embedded OTL, in which case mantra cannot access it, so the file will still be embedded in the .ifd. OTLs are loaded by mantra in exactly the same way that they are loaded by Houdini. When doing network rendering, this means that the rendering machines must have access to the same OTLs as the source machine.

When using SHOPs defined in OTLs or using the Render From File option on an object, or using a texture map where the file is embedded in an operator definition in an OTL, the data is no longer embedded in the .ifd file. Instead, mantra is now capable of reading files using the opdef: syntax. The exception to this is if the operator type definition is part of the Embedded OTL, in which case mantra cannot access it, so the file will still be embedded in the .ifd. OTLs are loaded by mantra in exactly the same way that they are loaded by Houdini. When doing network rendering, this means that the rendering machines must have access to the same OTLs as the source machine.

When using SHOPs defined in OTLs or using the Render From File option on an object, or using a texture map where the file is embedded in an operator definition in an OTL, the data is no longer embedded in the .ifd file. Instead, mantra is now capable of reading files using the opdef: syntax. The exception to this is if the operator type definition is part of the Embedded OTL, in which case mantra cannot access it, so the file will still be embedded in the .ifd. OTLs are loaded by mantra in exactly the same way that they are loaded by Houdini. When doing network rendering, this means that the rendering machines must have access to the same OTLs as the source machine.

When using SHOPs defined in OTLs or using the Render From File option on an object, or using a texture map where the file is embedded in an operator definition in an OTL, the data is no longer embedded in the .ifd file. Instead, mantra is now capable of reading files using the opdef: syntax. The exception to this is if the operator type definition is part of the Embedded OTL, in which case mantra cannot access it, so the file will still be embedded in the .ifd. OTLs are loaded by mantra in exactly the same way that they are loaded by Houdini. When doing network rendering, this means that the rendering machines must have access to the same OTLs as the source machine.

When using SHOPs defined in OTLs or using the Render From File option on an object, or using a texture map where the file is embedded in an operator definition in an OTL, the data is no longer embedded in the .ifd file. Instead, mantra is now capable of reading files using the opdef: syntax. The exception to this is if the operator type definition is part of the Embedded OTL, in which case mantra cannot access it, so the file will still be embedded in the .ifd. OTLs are loaded by mantra in exactly the same way that they are loaded by Houdini. When doing network rendering, this means that the rendering machines must have access to the same OTLs as the source machine.

Improved the memory efficiency of OTLs. Previously any operator type definition from an OTL that was actually used in a hip file would be completely loaded into RAM. This is no longer the case. Instead, information is always kept on disk and read in only when it is required. This is especially useful for operator type definitions that embed a number of geometry or image files.

Improved the memory efficiency of OTLs. Previously any operator type definition from an OTL that was actually used in a hip file would be completely loaded into RAM. This is no longer the case. Instead, information is always kept on disk and read in only when it is required. This is especially useful for operator type definitions that embed a number of geometry or image files.

Improved the memory efficiency of OTLs. Previously any operator type definition from an OTL that was actually used in a hip file would be completely loaded into RAM. This is no longer the case. Instead, information is always kept on disk and read in only when it is required. This is especially useful for operator type definitions that embed a number of geometry or image files.

Improved the memory efficiency of OTLs. Previously any operator type definition from an OTL that was actually used in a hip file would be completely loaded into RAM. This is no longer the case. Instead, information is always kept on disk and read in only when it is required. This is especially useful for operator type definitions that embed a number of geometry or image files.

Improved the memory efficiency of OTLs. Previously any operator type definition from an OTL that was actually used in a hip file would be completely loaded into RAM. This is no longer the case. Instead, information is always kept on disk and read in only when it is required. This is especially useful for operator type definitions that embed a number of geometry or image files.

Many of the HDK sample files shipped with 6.0 did not compile due to changes in the HDK. Many of the samples are now up to date (with the exception of SOP_CopRaster.C) which will probably be obsoleted or changed dramatically in the near future.