A new global objects option has been added to allow Keep Position When Moving. When enabled, changing the transform of an object will automatically modify its output objects to maintain the same world transform.

A new global objects option has been added to allow Keep Position When Moving. When enabled, changing the transform of an object will automatically modify its output objects to maintain the same world transform.

A new global objects option has been added to allow Keep Position When Moving. When enabled, changing the transform of an object will automatically modify its output objects to maintain the same world transform.

When user is in Pose state (or Transform or certain other states) and clicks on CTRL + MMB, the bottom blue help bar will now be populated with the name of the node the cursor is pointing at.

When user is in Pose state (or Transform or certain other states) and clicks on CTRL + MMB, the bottom blue help bar will now be populated with the name of the node the cursor is pointing at.

When user is in Pose state (or Transform or certain other states) and clicks on CTRL + MMB, the bottom blue help bar will now be populated with the name of the node the cursor is pointing at.

When user is in Pose state (or Transform or certain other states) and clicks on CTRL + MMB, the bottom blue help bar will now be populated with the name of the node the cursor is pointing at.

When user is in Pose state (or Transform or certain other states) and clicks on CTRL + MMB, the bottom blue help bar will now be populated with the name of the node the cursor is pointing at.

When user attempts to load a custom color palette file which contains lines with formatting errors, Houdini will pop up a text dialog detailing the problem. To clarify a previous point: If there are problematic lines in a palette file, those lines will be skipped, but the remainder of the file will still be loaded properly.

When user attempts to load a custom color palette file which contains lines with formatting errors, Houdini will pop up a text dialog detailing the problem. To clarify a previous point: If there are problematic lines in a palette file, those lines will be skipped, but the remainder of the file will still be loaded properly.

When user attempts to load a custom color palette file which contains lines with formatting errors, Houdini will pop up a text dialog detailing the problem. To clarify a previous point: If there are problematic lines in a palette file, those lines will be skipped, but the remainder of the file will still be loaded properly.

When user attempts to load a custom color palette file which contains lines with formatting errors, Houdini will pop up a text dialog detailing the problem. To clarify a previous point: If there are problematic lines in a palette file, those lines will be skipped, but the remainder of the file will still be loaded properly.

When user attempts to load a custom color palette file which contains lines with formatting errors, Houdini will pop up a text dialog detailing the problem. To clarify a previous point: If there are problematic lines in a palette file, those lines will be skipped, but the remainder of the file will still be loaded properly.

Labels and Separators are now included in the parm types the Type Properties parameter editor. They are merely cosmetic to the OP.

Labels and Separators are now included in the parm types the Type Properties parameter editor. They are merely cosmetic to the OP.

Labels and Separators are now included in the parm types the Type Properties parameter editor. They are merely cosmetic to the OP.

Labels and Separators are now included in the parm types the Type Properties parameter editor. They are merely cosmetic to the OP.

Labels and Separators are now included in the parm types the Type Properties parameter editor. They are merely cosmetic to the OP.

resizeable audio viewer in JIVE

resizeable audio viewer in JIVE

resizeable audio viewer in JIVE

resizeable audio viewer in JIVE

resizeable audio viewer in JIVE

Fixed a problem with textures sourced from COPs using the op: syntax not properly updating, even though the COPnet was cooking.

It is now possible to log the text of Houdini errors and messages to an external file using the HOUDINI_ERRORLOG_FILENAME and HOUDINI_ERRORLOG_LEVEL environment variables. See hconfig -h for more information.