Added two new DSO search paths, HOUDINI_IMAGE_DSO_PATH and HOUDINI_AUDIO_DSO_PATH, responsible for loading image formats and audio formats, respectively. This introduces a slight backwards incompatibility as now all custom image formats must be in an 'fb' subdirectory.

This allows MPlay to load image formats and audio formats without printing errors for other DSO types which cannot be loaded (because MPlay is linked against fewer Houdini libraries, to improve startup time).

Added two new DSO search paths, HOUDINI_IMAGE_DSO_PATH and HOUDINI_AUDIO_DSO_PATH, responsible for loading image formats and audio formats, respectively. This introduces a slight backwards incompatibility as now all custom image formats must be in an 'fb' subdirectory.

This allows MPlay to load image formats and audio formats without printing errors for other DSO types which cannot be loaded (because MPlay is linked against fewer Houdini libraries, to improve startup time).

Added two new DSO search paths, HOUDINI_IMAGE_DSO_PATH and HOUDINI_AUDIO_DSO_PATH, responsible for loading image formats and audio formats, respectively. This introduces a slight backwards incompatibility as now all custom image formats must be in an 'fb' subdirectory.

This allows MPlay to load image formats and audio formats without printing errors for other DSO types which cannot be loaded (because MPlay is linked against fewer Houdini libraries, to improve startup time).

Added two new DSO search paths, HOUDINI_IMAGE_DSO_PATH and HOUDINI_AUDIO_DSO_PATH, responsible for loading image formats and audio formats, respectively. This introduces a slight backwards incompatibility as now all custom image formats must be in an 'fb' subdirectory.

This allows MPlay to load image formats and audio formats without printing errors for other DSO types which cannot be loaded (because MPlay is linked against fewer Houdini libraries, to improve startup time).

Added two new DSO search paths, HOUDINI_IMAGE_DSO_PATH and HOUDINI_AUDIO_DSO_PATH, responsible for loading image formats and audio formats, respectively. This introduces a slight backwards incompatibility as now all custom image formats must be in an 'fb' subdirectory.

This allows MPlay to load image formats and audio formats without printing errors for other DSO types which cannot be loaded (because MPlay is linked against fewer Houdini libraries, to improve startup time).

Fixed bug when duplicating a folder parameter with nest folders in the Type Properties dialog.

Fixed bug when duplicating a folder parameter with nest folders in the Type Properties dialog.

Fixed bug when duplicating a folder parameter with nest folders in the Type Properties dialog.

Fixed bug when duplicating a folder parameter with nest folders in the Type Properties dialog.

Fixed bug when duplicating a folder parameter with nest folders in the Type Properties dialog.

VEX now has varying support for strings. Previously, a string would have had to be constant (the same value) over all points being modified. It's now possible to have different strings for each point in the geometry.

Primarily, this is useful in SOPs and POPs where it's now possible to override parameter values with string attributes and also create string attributes by using the export keyword.

Currently, not all functions which process strings in VEX can handle varying strings and some functions will just use one string as a uniform (constant) value. The functions which currently support varying strings are:

• optransform()
• ch()
• strlen()
• match()
• atoi()
• atof()
• concat()
• sprintf()

For example,

sop createinstance(export string instance="") { instance = sprintf("file%d.bgeo", floor(random(ptnum)*10)); }

would create an attribute called "instance" which would have a random file assigned to each point in the geometry.

VEX now has varying support for strings. Previously, a string would have had to be constant (the same value) over all points being modified. It's now possible to have different strings for each point in the geometry.

Primarily, this is useful in SOPs and POPs where it's now possible to override parameter values with string attributes and also create string attributes by using the export keyword.

Currently, not all functions which process strings in VEX can handle varying strings and some functions will just use one string as a uniform (constant) value. The functions which currently support varying strings are:

• optransform()
• ch()
• strlen()
• match()
• atoi()
• atof()
• concat()
• sprintf()

For example,

sop createinstance(export string instance="") { instance = sprintf("file%d.bgeo", floor(random(ptnum)*10)); }

would create an attribute called "instance" which would have a random file assigned to each point in the geometry.

VEX now has varying support for strings. Previously, a string would have had to be constant (the same value) over all points being modified. It's now possible to have different strings for each point in the geometry.

Primarily, this is useful in SOPs and POPs where it's now possible to override parameter values with string attributes and also create string attributes by using the export keyword.

Currently, not all functions which process strings in VEX can handle varying strings and some functions will just use one string as a uniform (constant) value. The functions which currently support varying strings are:

• optransform()
• ch()
• strlen()
• match()
• atoi()
• atof()
• concat()
• sprintf()

For example,

sop createinstance(export string instance="") { instance = sprintf("file%d.bgeo", floor(random(ptnum)*10)); }

would create an attribute called "instance" which would have a random file assigned to each point in the geometry.

VEX now has varying support for strings. Previously, a string would have had to be constant (the same value) over all points being modified. It's now possible to have different strings for each point in the geometry.

Primarily, this is useful in SOPs and POPs where it's now possible to override parameter values with string attributes and also create string attributes by using the export keyword.

Currently, not all functions which process strings in VEX can handle varying strings and some functions will just use one string as a uniform (constant) value. The functions which currently support varying strings are:

• optransform()
• ch()
• strlen()
• match()
• atoi()
• atof()
• concat()
• sprintf()

For example,

sop createinstance(export string instance="") { instance = sprintf("file%d.bgeo", floor(random(ptnum)*10)); }

would create an attribute called "instance" which would have a random file assigned to each point in the geometry.

VEX now has varying support for strings. Previously, a string would have had to be constant (the same value) over all points being modified. It's now possible to have different strings for each point in the geometry.

Primarily, this is useful in SOPs and POPs where it's now possible to override parameter values with string attributes and also create string attributes by using the export keyword.

Currently, not all functions which process strings in VEX can handle varying strings and some functions will just use one string as a uniform (constant) value. The functions which currently support varying strings are:

• optransform()
• ch()
• strlen()
• match()
• atoi()
• atof()
• concat()
• sprintf()

For example,

sop createinstance(export string instance="") { instance = sprintf("file%d.bgeo", floor(random(ptnum)*10)); }

would create an attribute called "instance" which would have a random file assigned to each point in the geometry.

The shading mode options in the 3D Viewer all now properly synchronize to each other.

The shading mode options in the 3D Viewer all now properly synchronize to each other.

The shading mode options in the 3D Viewer all now properly synchronize to each other.

The shading mode options in the 3D Viewer all now properly synchronize to each other.

The shading mode options in the 3D Viewer all now properly synchronize to each other.

The environment variables now disable the functionality when set to 1 instead of 0: HOUDINI_DISABLE_MMX HOUDINI_DISABLE_XMMX HOUDINI_DISABLE_SSE HOUDINI_DISABLE_3DNOW

The environment variables now disable the functionality when set to 1 instead of 0: HOUDINI_DISABLE_MMX HOUDINI_DISABLE_XMMX HOUDINI_DISABLE_SSE HOUDINI_DISABLE_3DNOW