Added the message command. Under hscript it is similar to the echo command except it always sends its output to standard output for the hscript executable. This means that even if this command is run through an open port, its output will go to the hscript console, not back to the calling process. In graphical Houdini applications, this command pops up a dialog box. Houdini will not do anything else until the user dismisses the dialog.

Added the message command. Under hscript it is similar to the echo command except it always sends its output to standard output for the hscript executable. This means that even if this command is run through an open port, its output will go to the hscript console, not back to the calling process. In graphical Houdini applications, this command pops up a dialog box. Houdini will not do anything else until the user dismisses the dialog.

Added the message command. Under hscript it is similar to the echo command except it always sends its output to standard output for the hscript executable. This means that even if this command is run through an open port, its output will go to the hscript console, not back to the calling process. In graphical Houdini applications, this command pops up a dialog box. Houdini will not do anything else until the user dismisses the dialog.

The java command help has been updated to match the current implementation, which includes the new -w option to wait until the java script execution has finished before returning from this command. The openport command also has a new -w option which prevents this command from returning until some external process sends a closeport command to close the port that was just opened.

The java command help has been updated to match the current implementation, which includes the new -w option to wait until the java script execution has finished before returning from this command. The openport command also has a new -w option which prevents this command from returning until some external process sends a closeport command to close the port that was just opened.

The java command help has been updated to match the current implementation, which includes the new -w option to wait until the java script execution has finished before returning from this command. The openport command also has a new -w option which prevents this command from returning until some external process sends a closeport command to close the port that was just opened.

The java command help has been updated to match the current implementation, which includes the new -w option to wait until the java script execution has finished before returning from this command. The openport command also has a new -w option which prevents this command from returning until some external process sends a closeport command to close the port that was just opened.

The java command help has been updated to match the current implementation, which includes the new -w option to wait until the java script execution has finished before returning from this command. The openport command also has a new -w option which prevents this command from returning until some external process sends a closeport command to close the port that was just opened.

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 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.