The smooth sop now allows the user to specify Texture UV or Color as target. In this way we apply the smoothing to the current layer. The user still has the option to specify the attribute name. Also we now use vertex attributes by default, and if not found, then we try for a point attribute.

The smooth sop now allows the user to specify Texture UV or Color as target. In this way we apply the smoothing to the current layer. The user still has the option to specify the attribute name. Also we now use vertex attributes by default, and if not found, then we try for a point attribute.

The smooth sop now allows the user to specify Texture UV or Color as target. In this way we apply the smoothing to the current layer. The user still has the option to specify the attribute name. Also we now use vertex attributes by default, and if not found, then we try for a point attribute.

The smooth sop now allows the user to specify Texture UV or Color as target. In this way we apply the smoothing to the current layer. The user still has the option to specify the attribute name. Also we now use vertex attributes by default, and if not found, then we try for a point attribute.

When rendering sequences of images from Houdini on Windows or Solaris (which support threaded UI), an interrupt dialog no longer pops up. Instead, the interrupt messages are sent to the main Houdini window.

When rendering sequences of images from Houdini on Windows or Solaris (which support threaded UI), an interrupt dialog no longer pops up. Instead, the interrupt messages are sent to the main Houdini window.

When rendering sequences of images from Houdini on Windows or Solaris (which support threaded UI), an interrupt dialog no longer pops up. Instead, the interrupt messages are sent to the main Houdini window.

When rendering sequences of images from Houdini on Windows or Solaris (which support threaded UI), an interrupt dialog no longer pops up. Instead, the interrupt messages are sent to the main Houdini window.

When rendering sequences of images from Houdini on Windows or Solaris (which support threaded UI), an interrupt dialog no longer pops up. Instead, the interrupt messages are sent to the main Houdini window.

Handles are now capable of remembering their settings. Per-op settings are saved to the hip file via a new "omparm" command. Also, starting a new operation will use the settings of the previous handle. For example, if you left the transform sop's handle in translate mode it will start up in translate mode the next time you put down another transform sop. Currently, the transform and edit sop handles are the only handles that remember their settings.

Handles are now capable of remembering their settings. Per-op settings are saved to the hip file via a new "omparm" command. Also, starting a new operation will use the settings of the previous handle. For example, if you left the transform sop's handle in translate mode it will start up in translate mode the next time you put down another transform sop. Currently, the transform and edit sop handles are the only handles that remember their settings.

Handles are now capable of remembering their settings. Per-op settings are saved to the hip file via a new "omparm" command. Also, starting a new operation will use the settings of the previous handle. For example, if you left the transform sop's handle in translate mode it will start up in translate mode the next time you put down another transform sop. Currently, the transform and edit sop handles are the only handles that remember their settings.

Handles are now capable of remembering their settings. Per-op settings are saved to the hip file via a new "omparm" command. Also, starting a new operation will use the settings of the previous handle. For example, if you left the transform sop's handle in translate mode it will start up in translate mode the next time you put down another transform sop. Currently, the transform and edit sop handles are the only handles that remember their settings.

Handles are now capable of remembering their settings. Per-op settings are saved to the hip file via a new "omparm" command. Also, starting a new operation will use the settings of the previous handle. For example, if you left the transform sop's handle in translate mode it will start up in translate mode the next time you put down another transform sop. Currently, the transform and edit sop handles are the only handles that remember their settings.

New UV Project sop which does best plane projection and automatic layout. Currently only works for vertex UVs. Still some work to be done.

New UV Project sop which does best plane projection and automatic layout. Currently only works for vertex UVs. Still some work to be done.

New UV Project sop which does best plane projection and automatic layout. Currently only works for vertex UVs. Still some work to be done.

New UV Project sop which does best plane projection and automatic layout. Currently only works for vertex UVs. Still some work to be done.

New UV Project sop which does best plane projection and automatic layout. Currently only works for vertex UVs. Still some work to be done.

There is a new command "shopvisible" which can hide operators for specific renderers in the toolbars. The operators still exist, but are not visible when adding new ops from the toolbar.

There is also a menu to control visibility of SHOPs in both the SHOP and Output Driver panes.

Please see the help for more information.

There is a new command "shopvisible" which can hide operators for specific renderers in the toolbars. The operators still exist, but are not visible when adding new ops from the toolbar.

There is also a menu to control visibility of SHOPs in both the SHOP and Output Driver panes.

Please see the help for more information.

There is a new command "shopvisible" which can hide operators for specific renderers in the toolbars. The operators still exist, but are not visible when adding new ops from the toolbar.

There is also a menu to control visibility of SHOPs in both the SHOP and Output Driver panes.

Please see the help for more information.

There is a new command "shopvisible" which can hide operators for specific renderers in the toolbars. The operators still exist, but are not visible when adding new ops from the toolbar.

There is also a menu to control visibility of SHOPs in both the SHOP and Output Driver panes.

Please see the help for more information.

There is a new command "shopvisible" which can hide operators for specific renderers in the toolbars. The operators still exist, but are not visible when adding new ops from the toolbar.

There is also a menu to control visibility of SHOPs in both the SHOP and Output Driver panes.

Please see the help for more information.

Edge selection is now rendered in the UV viewport for vertex attributes.