The VEX shadowmap() function has been modified and will now produce much better results in shading contexts. However, due to changes in the code:

• The spread value may be slightly different than priorversions.
• The optional arguments to control the filter width are nowrecognized and can be used to bias the shadow spread.

Images rendered using shadow maps will be quite different.

The VEX shadowmap() function has been modified and will now produce much better results in shading contexts. However, due to changes in the code:

• The spread value may be slightly different than priorversions.
• The optional arguments to control the filter width are nowrecognized and can be used to bias the shadow spread.

Images rendered using shadow maps will be quite different.

The VEX shadowmap() function has been modified and will now produce much better results in shading contexts. However, due to changes in the code:

• The spread value may be slightly different than priorversions.
• The optional arguments to control the filter width are nowrecognized and can be used to bias the shadow spread.

Images rendered using shadow maps will be quite different.

The VEX shadowmap() function has been modified and will now produce much better results in shading contexts. However, due to changes in the code:

• The spread value may be slightly different than priorversions.
• The optional arguments to control the filter width are nowrecognized and can be used to bias the shadow spread.

Images rendered using shadow maps will be quite different.

The VEX shadowmap() function has been modified and will now produce much better results in shading contexts. However, due to changes in the code:

• The spread value may be slightly different than priorversions.
• The optional arguments to control the filter width are nowrecognized and can be used to bias the shadow spread.

Images rendered using shadow maps will be quite different.

There was a problem when running VEX code recursively (typically in mantra due to reflections, refractions, etc.) when parameters had been overridden by geometry attributes.

There was a problem when running VEX code recursively (typically in mantra due to reflections, refractions, etc.) when parameters had been overridden by geometry attributes.

There was a problem when running VEX code recursively (typically in mantra due to reflections, refractions, etc.) when parameters had been overridden by geometry attributes.

There was a problem when running VEX code recursively (typically in mantra due to reflections, refractions, etc.) when parameters had been overridden by geometry attributes.

There was a problem when running VEX code recursively (typically in mantra due to reflections, refractions, etc.) when parameters had been overridden by geometry attributes.

Blend object enhancements:

• Added "Shortest Path Rotation Blending" option for sequence blending
• Made it an multi-input object since sequence blending can work with an arbitrarynumber of parents.

Blend object enhancements:

• Added "Shortest Path Rotation Blending" option for sequence blending
• Made it an multi-input object since sequence blending can work with an arbitrarynumber of parents.

Blend object enhancements:

• Added "Shortest Path Rotation Blending" option for sequence blending
• Made it an multi-input object since sequence blending can work with an arbitrarynumber of parents.

Blend object enhancements:

• Added "Shortest Path Rotation Blending" option for sequence blending
• Made it an multi-input object since sequence blending can work with an arbitrarynumber of parents.

Blend object enhancements:

• Added "Shortest Path Rotation Blending" option for sequence blending
• Made it an multi-input object since sequence blending can work with an arbitrarynumber of parents.

Index attributes with names, as those created by AttribCreate and the String type, will be read as the string name, not the number that corresponds to the string.

Index attributes with names, as those created by AttribCreate and the String type, will be read as the string name, not the number that corresponds to the string.

Index attributes with names, as those created by AttribCreate and the String type, will be read as the string name, not the number that corresponds to the string.

Index attributes with names, as those created by AttribCreate and the String type, will be read as the string name, not the number that corresponds to the string.

Index attributes with names, as those created by AttribCreate and the String type, will be read as the string name, not the number that corresponds to the string.

Fixed an incorrect assertion (and potential problems) with picking when there is a handle or a menu in the viewport.

Fixed an incorrect assertion (and potential problems) with picking when there is a handle or a menu in the viewport.