Mostly for doc and tutotial writers: the word "state" has been eliminated from the interfce and has been replaced with "tool". Thus, all interactive operations in Houdini are now called "tools".

Mostly for doc and tutotial writers: the word "state" has been eliminated from the interfce and has been replaced with "tool". Thus, all interactive operations in Houdini are now called "tools".

Mostly for doc and tutotial writers: the word "state" has been eliminated from the interfce and has been replaced with "tool". Thus, all interactive operations in Houdini are now called "tools".

Mostly for doc and tutotial writers: the word "state" has been eliminated from the interfce and has been replaced with "tool". Thus, all interactive operations in Houdini are now called "tools".

When holding a right-mouse click over emptiness in the Object/SOP viewers, the "Nothing is pickable" menu no longer appears. This allows the user to continue on with right-mouse dragging.

When holding a right-mouse click over emptiness in the Object/SOP viewers, the "Nothing is pickable" menu no longer appears. This allows the user to continue on with right-mouse dragging.

When holding a right-mouse click over emptiness in the Object/SOP viewers, the "Nothing is pickable" menu no longer appears. This allows the user to continue on with right-mouse dragging.

When holding a right-mouse click over emptiness in the Object/SOP viewers, the "Nothing is pickable" menu no longer appears. This allows the user to continue on with right-mouse dragging.

When holding a right-mouse click over emptiness in the Object/SOP viewers, the "Nothing is pickable" menu no longer appears. This allows the user to continue on with right-mouse dragging.

The quit command in hscript will now prompt the user to confirm termination. This behaviour can be overridden with the -f option. If the quit command occurs within a script, the response to the quit command will be read from the next line in the script. For example:

# # hscript quit command # set RESPONSE = yes quit $RESPONSE

If hscript is not started interactively (i.e. reading from a pipe or I/O redirection), the quit command will not prompt for confirmation.

The quit command in hscript will now prompt the user to confirm termination. This behaviour can be overridden with the -f option. If the quit command occurs within a script, the response to the quit command will be read from the next line in the script. For example:

# # hscript quit command # set RESPONSE = yes quit $RESPONSE

If hscript is not started interactively (i.e. reading from a pipe or I/O redirection), the quit command will not prompt for confirmation.

The quit command in hscript will now prompt the user to confirm termination. This behaviour can be overridden with the -f option. If the quit command occurs within a script, the response to the quit command will be read from the next line in the script. For example:

# # hscript quit command # set RESPONSE = yes quit $RESPONSE

If hscript is not started interactively (i.e. reading from a pipe or I/O redirection), the quit command will not prompt for confirmation.

The quit command in hscript will now prompt the user to confirm termination. This behaviour can be overridden with the -f option. If the quit command occurs within a script, the response to the quit command will be read from the next line in the script. For example:

# # hscript quit command # set RESPONSE = yes quit $RESPONSE

If hscript is not started interactively (i.e. reading from a pipe or I/O redirection), the quit command will not prompt for confirmation.

The quit command in hscript will now prompt the user to confirm termination. This behaviour can be overridden with the -f option. If the quit command occurs within a script, the response to the quit command will be read from the next line in the script. For example:

# # hscript quit command # set RESPONSE = yes quit $RESPONSE

If hscript is not started interactively (i.e. reading from a pipe or I/O redirection), the quit command will not prompt for confirmation.

Fixing bug where bypassing and un-bypassing a subnet SOP would leave the subnet with no geometry.

Fixing bug where bypassing and un-bypassing a subnet SOP would leave the subnet with no geometry.

Fixing bug where bypassing and un-bypassing a subnet SOP would leave the subnet with no geometry.

Fixing bug where bypassing and un-bypassing a subnet SOP would leave the subnet with no geometry.

Fixing bug where bypassing and un-bypassing a subnet SOP would leave the subnet with no geometry.

Ctrl+c/v hotkeys have been enabled for the graph mode of the channel editor. They do the same as the C/P buttons in the upper-right corner. ie. copy the values at the current time and paste the previously copied values at the current time.