The interface to mantra procedurals has changed. The level of detail is no longer passed through the render() method and needs to be computed by the procedural using getLevelOfDetail().

The interface to mantra procedurals has changed. The level of detail is no longer passed through the render() method and needs to be computed by the procedural using getLevelOfDetail().

The interface to mantra procedurals has changed. The level of detail is no longer passed through the render() method and needs to be computed by the procedural using getLevelOfDetail().

The interface to mantra procedurals has changed. The level of detail is no longer passed through the render() method and needs to be computed by the procedural using getLevelOfDetail().

The POP Solver DOP has additional options to turn off different stages of the POP Solver pipeline. The new Solver Tab allows you to avoid time integration, particle deletion, or particle prepping. It also allows you to specify data other than Geometry to work with. This allows one to use POPs to update the behaviour of geometry without adding all of the simulation aspects that might be already handled by other nodes.

The POP Solver DOP has additional options to turn off different stages of the POP Solver pipeline. The new Solver Tab allows you to avoid time integration, particle deletion, or particle prepping. It also allows you to specify data other than Geometry to work with. This allows one to use POPs to update the behaviour of geometry without adding all of the simulation aspects that might be already handled by other nodes.

The POP Solver DOP has additional options to turn off different stages of the POP Solver pipeline. The new Solver Tab allows you to avoid time integration, particle deletion, or particle prepping. It also allows you to specify data other than Geometry to work with. This allows one to use POPs to update the behaviour of geometry without adding all of the simulation aspects that might be already handled by other nodes.

The POP Solver DOP has additional options to turn off different stages of the POP Solver pipeline. The new Solver Tab allows you to avoid time integration, particle deletion, or particle prepping. It also allows you to specify data other than Geometry to work with. This allows one to use POPs to update the behaviour of geometry without adding all of the simulation aspects that might be already handled by other nodes.

The POP Solver DOP has additional options to turn off different stages of the POP Solver pipeline. The new Solver Tab allows you to avoid time integration, particle deletion, or particle prepping. It also allows you to specify data other than Geometry to work with. This allows one to use POPs to update the behaviour of geometry without adding all of the simulation aspects that might be already handled by other nodes.

When creating a path using the object viewer's Path tool, the PathCV objects are now created such that their +X axis are aligned with the viewing plane's normal instead of the -Y axis. This ensures that a bone chain that is drawn in the same fashion won't "pop" when an InverseKin CHOP is applied using Follow Curve.

When creating a path using the object viewer's Path tool, the PathCV objects are now created such that their +X axis are aligned with the viewing plane's normal instead of the -Y axis. This ensures that a bone chain that is drawn in the same fashion won't "pop" when an InverseKin CHOP is applied using Follow Curve.

When creating a path using the object viewer's Path tool, the PathCV objects are now created such that their +X axis are aligned with the viewing plane's normal instead of the -Y axis. This ensures that a bone chain that is drawn in the same fashion won't "pop" when an InverseKin CHOP is applied using Follow Curve.

When creating a path using the object viewer's Path tool, the PathCV objects are now created such that their +X axis are aligned with the viewing plane's normal instead of the -Y axis. This ensures that a bone chain that is drawn in the same fashion won't "pop" when an InverseKin CHOP is applied using Follow Curve.

When creating a path using the object viewer's Path tool, the PathCV objects are now created such that their +X axis are aligned with the viewing plane's normal instead of the -Y axis. This ensures that a bone chain that is drawn in the same fashion won't "pop" when an InverseKin CHOP is applied using Follow Curve.

The CPP processor in Houdini has a new directive "sinclude" which is identical to "include", except that no error is generated if the file is inaccessible.

This is used in the soho parameter definitions to allow for per-job/user/site collections of parameters to be defined.

The CPP processor in Houdini has a new directive "sinclude" which is identical to "include", except that no error is generated if the file is inaccessible.

This is used in the soho parameter definitions to allow for per-job/user/site collections of parameters to be defined.

The CPP processor in Houdini has a new directive "sinclude" which is identical to "include", except that no error is generated if the file is inaccessible.

This is used in the soho parameter definitions to allow for per-job/user/site collections of parameters to be defined.

The CPP processor in Houdini has a new directive "sinclude" which is identical to "include", except that no error is generated if the file is inaccessible.

This is used in the soho parameter definitions to allow for per-job/user/site collections of parameters to be defined.

The CPP processor in Houdini has a new directive "sinclude" which is identical to "include", except that no error is generated if the file is inaccessible.

This is used in the soho parameter definitions to allow for per-job/user/site collections of parameters to be defined.

Fixed examples in the help documentation for the stamps() expression.

Fixed examples in the help documentation for the stamps() expression.

Fixed examples in the help documentation for the stamps() expression.

Fixed examples in the help documentation for the stamps() expression.

Fixed examples in the help documentation for the stamps() expression.

Using Shift rather than Ctrl for accepting selection and toggling input fields between their last two values. Ie, using Shift+RMB instead of Ctrl+RMB.