All channels are created with the "Extend" behaviour rather than "Hold" behaviour. This means outside their defined frame ranges the closest segment's expression is evaluated instead of just propogating its last value. This is very useful for many expressions which are frame independent.

All channels are created with the "Extend" behaviour rather than "Hold" behaviour. This means outside their defined frame ranges the closest segment's expression is evaluated instead of just propogating its last value. This is very useful for many expressions which are frame independent.

All channels are created with the "Extend" behaviour rather than "Hold" behaviour. This means outside their defined frame ranges the closest segment's expression is evaluated instead of just propogating its last value. This is very useful for many expressions which are frame independent.

All channels are created with the "Extend" behaviour rather than "Hold" behaviour. This means outside their defined frame ranges the closest segment's expression is evaluated instead of just propogating its last value. This is very useful for many expressions which are frame independent.

All channels are created with the "Extend" behaviour rather than "Hold" behaviour. This means outside their defined frame ranges the closest segment's expression is evaluated instead of just propogating its last value. This is very useful for many expressions which are frame independent.

• The PolySplit SOP should now run quite a bit faster.
• Fix bug: when cutting across a vertex, some polygons in between may havebeen missed.
• Fix bug: when doing a complicated cut with many possible paths, sometimesa good path node was being erroneously deleted.

• The PolySplit SOP should now run quite a bit faster.
• Fix bug: when cutting across a vertex, some polygons in between may havebeen missed.
• Fix bug: when doing a complicated cut with many possible paths, sometimesa good path node was being erroneously deleted.

• The PolySplit SOP should now run quite a bit faster.
• Fix bug: when cutting across a vertex, some polygons in between may havebeen missed.
• Fix bug: when doing a complicated cut with many possible paths, sometimesa good path node was being erroneously deleted.

• The PolySplit SOP should now run quite a bit faster.
• Fix bug: when cutting across a vertex, some polygons in between may havebeen missed.
• Fix bug: when doing a complicated cut with many possible paths, sometimesa good path node was being erroneously deleted.

• The PolySplit SOP should now run quite a bit faster.
• Fix bug: when cutting across a vertex, some polygons in between may havebeen missed.
• Fix bug: when doing a complicated cut with many possible paths, sometimesa good path node was being erroneously deleted.

The viewdisplay command can now be used to change shading modes (and point display, etc.) for unselected geometry, selected geometry, templates, and target output. Scripts that change the shading mode can now be tied to function keys. This should help to make subdivision surface modeling easier.

The viewdisplay command can now be used to change shading modes (and point display, etc.) for unselected geometry, selected geometry, templates, and target output. Scripts that change the shading mode can now be tied to function keys. This should help to make subdivision surface modeling easier.

The viewdisplay command can now be used to change shading modes (and point display, etc.) for unselected geometry, selected geometry, templates, and target output. Scripts that change the shading mode can now be tied to function keys. This should help to make subdivision surface modeling easier.

The viewdisplay command can now be used to change shading modes (and point display, etc.) for unselected geometry, selected geometry, templates, and target output. Scripts that change the shading mode can now be tied to function keys. This should help to make subdivision surface modeling easier.

The viewdisplay command can now be used to change shading modes (and point display, etc.) for unselected geometry, selected geometry, templates, and target output. Scripts that change the shading mode can now be tied to function keys. This should help to make subdivision surface modeling easier.

Pressing the reselect button to select the inputs to a sop will preselect the geometry that is currently input to the sop.

Pressing the reselect button to select the inputs to a sop will preselect the geometry that is currently input to the sop.

Pressing the reselect button to select the inputs to a sop will preselect the geometry that is currently input to the sop.

Pressing the reselect button to select the inputs to a sop will preselect the geometry that is currently input to the sop.

Pressing the reselect button to select the inputs to a sop will preselect the geometry that is currently input to the sop.

Handle, Microphone, Null and Sound objects can no longer be sent to renderers. These objects have no shading/lighting parameters visible and thus can be considered to be non-renderable. Previously, if a Null object were displayed at render time, the light mask of the Null object might have caused depth maps to be auto-generated from light sources fallaciously.

Handle, Microphone, Null and Sound objects can no longer be sent to renderers. These objects have no shading/lighting parameters visible and thus can be considered to be non-renderable. Previously, if a Null object were displayed at render time, the light mask of the Null object might have caused depth maps to be auto-generated from light sources fallaciously.

Handle, Microphone, Null and Sound objects can no longer be sent to renderers. These objects have no shading/lighting parameters visible and thus can be considered to be non-renderable. Previously, if a Null object were displayed at render time, the light mask of the Null object might have caused depth maps to be auto-generated from light sources fallaciously.

Handle, Microphone, Null and Sound objects can no longer be sent to renderers. These objects have no shading/lighting parameters visible and thus can be considered to be non-renderable. Previously, if a Null object were displayed at render time, the light mask of the Null object might have caused depth maps to be auto-generated from light sources fallaciously.

Handle, Microphone, Null and Sound objects can no longer be sent to renderers. These objects have no shading/lighting parameters visible and thus can be considered to be non-renderable. Previously, if a Null object were displayed at render time, the light mask of the Null object might have caused depth maps to be auto-generated from light sources fallaciously.