Channel references are now properly followed and hilighted when its associated handle is active. Locked parameters can no longer be hilighted.

Channel references are now properly followed and hilighted when its associated handle is active. Locked parameters can no longer be hilighted.

Channel references are now properly followed and hilighted when its associated handle is active. Locked parameters can no longer be hilighted.

Channel references are now properly followed and hilighted when its associated handle is active. Locked parameters can no longer be hilighted.

The global preference for "Avoid Setting Pre-Transforms" has been replaced with the "Ignore Pre-Transforms" setting. Not only will this setting avoid setting pre-transforms, it will also ignore them even if they exist.

The global preference for "Avoid Setting Pre-Transforms" has been replaced with the "Ignore Pre-Transforms" setting. Not only will this setting avoid setting pre-transforms, it will also ignore them even if they exist.

The global preference for "Avoid Setting Pre-Transforms" has been replaced with the "Ignore Pre-Transforms" setting. Not only will this setting avoid setting pre-transforms, it will also ignore them even if they exist.

The global preference for "Avoid Setting Pre-Transforms" has been replaced with the "Ignore Pre-Transforms" setting. Not only will this setting avoid setting pre-transforms, it will also ignore them even if they exist.

The global preference for "Avoid Setting Pre-Transforms" has been replaced with the "Ignore Pre-Transforms" setting. Not only will this setting avoid setting pre-transforms, it will also ignore them even if they exist.

The global preference for "Avoid Setting Pre-Transforms" has been replaced with the "Ignore Pre-Transforms" setting. Not only will this setting avoid setting pre-transforms, it will also ignore them even if they exist.

There is now a new hscript command, chopexportmap which allows manipulation of custom chop override mappings. The opscript command now also outputs this so that chop nodes are now faithfully reproduced.

There is now a new hscript command, chopexportmap which allows manipulation of custom chop override mappings. The opscript command now also outputs this so that chop nodes are now faithfully reproduced.

There is now a new hscript command, chopexportmap which allows manipulation of custom chop override mappings. The opscript command now also outputs this so that chop nodes are now faithfully reproduced.

There is now a new hscript command, chopexportmap which allows manipulation of custom chop override mappings. The opscript command now also outputs this so that chop nodes are now faithfully reproduced.

There is now a new hscript command, chopexportmap which allows manipulation of custom chop override mappings. The opscript command now also outputs this so that chop nodes are now faithfully reproduced.

There is now a new hscript command, chopexportmap which allows manipulation of custom chop override mappings. The opscript command now also outputs this so that chop nodes are now faithfully reproduced.

Cutting and pasting nodes will now properly update the pane path.

Cutting and pasting nodes will now properly update the pane path.

Cutting and pasting nodes will now properly update the pane path.

Cutting and pasting nodes will now properly update the pane path.

Cutting and pasting nodes will now properly update the pane path.

Cutting and pasting nodes will now properly update the pane path.

Added ability for the user to choose custom color palettes from a menu. The palettes must be stored in a folder called .../config/ColorPalettes. The palette files themselves can have any name or extension, and they must follow the original X11 palette file's format. Note: This will not break legacy Houdini behaviour, i.e. the user should NOT move the original X11 palette file from its original location.

Added ability for the user to choose custom color palettes from a menu. The palettes must be stored in a folder called .../config/ColorPalettes. The palette files themselves can have any name or extension, and they must follow the original X11 palette file's format. Note: This will not break legacy Houdini behaviour, i.e. the user should NOT move the original X11 palette file from its original location.

Added ability for the user to choose custom color palettes from a menu. The palettes must be stored in a folder called .../config/ColorPalettes. The palette files themselves can have any name or extension, and they must follow the original X11 palette file's format. Note: This will not break legacy Houdini behaviour, i.e. the user should NOT move the original X11 palette file from its original location.