Fixed bug where undoing set key operations on a scoped channel would cause it to become unscoped.

Fixed bug where undoing set key operations on a scoped channel would cause it to become unscoped.

Fixed bug where undoing set key operations on a scoped channel would cause it to become unscoped.

Fixed bug where undoing set key operations on a scoped channel would cause it to become unscoped.

The libraries MSS and PI have been opened up in the HDK. This, combined with a few other changes, means it is now possible to make HDK SOPs which have the Brush interface (like the Paint, Comb, Sculpt, etc SOPs). For an example, look at the SOP_BrushHairLen example in the HDK samples.

The libraries MSS and PI have been opened up in the HDK. This, combined with a few other changes, means it is now possible to make HDK SOPs which have the Brush interface (like the Paint, Comb, Sculpt, etc SOPs). For an example, look at the SOP_BrushHairLen example in the HDK samples.

The libraries MSS and PI have been opened up in the HDK. This, combined with a few other changes, means it is now possible to make HDK SOPs which have the Brush interface (like the Paint, Comb, Sculpt, etc SOPs). For an example, look at the SOP_BrushHairLen example in the HDK samples.

The libraries MSS and PI have been opened up in the HDK. This, combined with a few other changes, means it is now possible to make HDK SOPs which have the Brush interface (like the Paint, Comb, Sculpt, etc SOPs). For an example, look at the SOP_BrushHairLen example in the HDK samples.

The libraries MSS and PI have been opened up in the HDK. This, combined with a few other changes, means it is now possible to make HDK SOPs which have the Brush interface (like the Paint, Comb, Sculpt, etc SOPs). For an example, look at the SOP_BrushHairLen example in the HDK samples.

Changed the behaviour of the parameter dialog to allow a user to modify a parameter for multiple nodes. When multiple nodes are selected in the network, the parameter dialog affects them all. Parameters in the selected nodes of the same name, type and size are changed together. The XCF causes the changes of numeric fields to be relative, while typing in a new value will set the absolute change. Other actions such as editing of the comments, delete scripts, dragging and dropping parameters, setting keys, deleting channels, and so forth also affect the selected set of nodes.

Changed the behaviour of the parameter dialog to allow a user to modify a parameter for multiple nodes. When multiple nodes are selected in the network, the parameter dialog affects them all. Parameters in the selected nodes of the same name, type and size are changed together. The XCF causes the changes of numeric fields to be relative, while typing in a new value will set the absolute change. Other actions such as editing of the comments, delete scripts, dragging and dropping parameters, setting keys, deleting channels, and so forth also affect the selected set of nodes.

Changed the behaviour of the parameter dialog to allow a user to modify a parameter for multiple nodes. When multiple nodes are selected in the network, the parameter dialog affects them all. Parameters in the selected nodes of the same name, type and size are changed together. The XCF causes the changes of numeric fields to be relative, while typing in a new value will set the absolute change. Other actions such as editing of the comments, delete scripts, dragging and dropping parameters, setting keys, deleting channels, and so forth also affect the selected set of nodes.

Changed the behaviour of the parameter dialog to allow a user to modify a parameter for multiple nodes. When multiple nodes are selected in the network, the parameter dialog affects them all. Parameters in the selected nodes of the same name, type and size are changed together. The XCF causes the changes of numeric fields to be relative, while typing in a new value will set the absolute change. Other actions such as editing of the comments, delete scripts, dragging and dropping parameters, setting keys, deleting channels, and so forth also affect the selected set of nodes.

Changed the behaviour of the parameter dialog to allow a user to modify a parameter for multiple nodes. When multiple nodes are selected in the network, the parameter dialog affects them all. Parameters in the selected nodes of the same name, type and size are changed together. The XCF causes the changes of numeric fields to be relative, while typing in a new value will set the absolute change. Other actions such as editing of the comments, delete scripts, dragging and dropping parameters, setting keys, deleting channels, and so forth also affect the selected set of nodes.

In the Global Animation Options dialogs, the minimum step size for non-integer frames has been decreased from 0.1 to 0.001.

In the Global Animation Options dialogs, the minimum step size for non-integer frames has been decreased from 0.1 to 0.001.

In the Global Animation Options dialogs, the minimum step size for non-integer frames has been decreased from 0.1 to 0.001.

In the Global Animation Options dialogs, the minimum step size for non-integer frames has been decreased from 0.1 to 0.001.

In the Global Animation Options dialogs, the minimum step size for non-integer frames has been decreased from 0.1 to 0.001.

It is now possible to create custom operator types with arbitrary nesting of parameters into folders, including having folders within other folders. This can be done using the Type Properties dialog, using the group pragma in VEX code (use "Foder 1/Folder 2" to indicate Folder 2 nested inside Folder 1), and in the VOP Network parameter order editor.

It is now possible to create custom operator types with arbitrary nesting of parameters into folders, including having folders within other folders. This can be done using the Type Properties dialog, using the group pragma in VEX code (use "Foder 1/Folder 2" to indicate Folder 2 nested inside Folder 1), and in the VOP Network parameter order editor.

It is now possible to create custom operator types with arbitrary nesting of parameters into folders, including having folders within other folders. This can be done using the Type Properties dialog, using the group pragma in VEX code (use "Foder 1/Folder 2" to indicate Folder 2 nested inside Folder 1), and in the VOP Network parameter order editor.