Fixed a bug that caused pragmas in vcc to stop evaluating arguments after a fixed number. This, for example, prevented group pragmas from adding more than 30 parameters to their group.

Fixed a bug that caused pragmas in vcc to stop evaluating arguments after a fixed number. This, for example, prevented group pragmas from adding more than 30 parameters to their group.

Fixed a bug that caused pragmas in vcc to stop evaluating arguments after a fixed number. This, for example, prevented group pragmas from adding more than 30 parameters to their group.

Fixed a bug that caused pragmas in vcc to stop evaluating arguments after a fixed number. This, for example, prevented group pragmas from adding more than 30 parameters to their group.

Flattened the look of the parameter spreadsheet to reduce the unnecessary clutter in the cells.

Flattened the look of the parameter spreadsheet to reduce the unnecessary clutter in the cells.

Flattened the look of the parameter spreadsheet to reduce the unnecessary clutter in the cells.

Flattened the look of the parameter spreadsheet to reduce the unnecessary clutter in the cells.

Flattened the look of the parameter spreadsheet to reduce the unnecessary clutter in the cells.

The license server log usage analyzer utility, sesiusage, now has a new -l option to output information for the minimum, maximum, median license usage times. It now always prints out the average license usage as well.

The license server log usage analyzer utility, sesiusage, now has a new -l option to output information for the minimum, maximum, median license usage times. It now always prints out the average license usage as well.

The license server log usage analyzer utility, sesiusage, now has a new -l option to output information for the minimum, maximum, median license usage times. It now always prints out the average license usage as well.

The license server log usage analyzer utility, sesiusage, now has a new -l option to output information for the minimum, maximum, median license usage times. It now always prints out the average license usage as well.

The license server log usage analyzer utility, sesiusage, now has a new -l option to output information for the minimum, maximum, median license usage times. It now always prints out the average license usage as well.

The license manager, sesinetd, will now correctly log "stats" (checks for existence of a license) as such instead of as license check outs.

The license manager, sesinetd, will now correctly log "stats" (checks for existence of a license) as such instead of as license check outs.

The license manager, sesinetd, will now correctly log "stats" (checks for existence of a license) as such instead of as license check outs.

The license manager, sesinetd, will now correctly log "stats" (checks for existence of a license) as such instead of as license check outs.

The license manager, sesinetd, will now correctly log "stats" (checks for existence of a license) as such instead of as license check outs.

Caching of grid data in mantra has been changed to use a disk cache. The cache will be created (if required) in the houdini tempororary directory (see hconfig HOUDINI_TEMP_DIR) and will be called mcache.XXX, where XXX is a unique identifier for the process being rendered.

When this cache is created, a warning will be output (with verbosity 1 or greater (command line option -V 1)).

The -G option controls the allowed memory before the cache file is created.

Previously, the -G option specified the number of grids to be created. Now, however, it specifies memory allowed. To keep a reasonable form of backwards compatibility, the option specifies a multiple of 4KB chunks of memory. Thus, -G 4096 (the default) allows 16 MB to be used before the disk cache is created.

The previous behaviour of mantra was to re-generate data if it was flushed out of RAM, which could have been prohibitive when expensive shading (such as global illumination) was involved in rendering.

Depending on disk speed (and if the HOUDINI_TEMP_DIR is local or networked), the new caching mechanism may prove to be more expensive than the re-generation of grid data. This behavour can be controlled on a per-object basis using the IFD command: ray_ocache, which takes exactly one argument. The argument should be "disk" or "regenerate".

WARNING: Not all data can be re-generated, meaning that even if all objects are set to the previous behaviour of regeneration of data, the disk cache file may still be constructed and used.

Caching of grid data in mantra has been changed to use a disk cache. The cache will be created (if required) in the houdini tempororary directory (see hconfig HOUDINI_TEMP_DIR) and will be called mcache.XXX, where XXX is a unique identifier for the process being rendered.

When this cache is created, a warning will be output (with verbosity 1 or greater (command line option -V 1)).

The -G option controls the allowed memory before the cache file is created.

Previously, the -G option specified the number of grids to be created. Now, however, it specifies memory allowed. To keep a reasonable form of backwards compatibility, the option specifies a multiple of 4KB chunks of memory. Thus, -G 4096 (the default) allows 16 MB to be used before the disk cache is created.

The previous behaviour of mantra was to re-generate data if it was flushed out of RAM, which could have been prohibitive when expensive shading (such as global illumination) was involved in rendering.

Depending on disk speed (and if the HOUDINI_TEMP_DIR is local or networked), the new caching mechanism may prove to be more expensive than the re-generation of grid data. This behavour can be controlled on a per-object basis using the IFD command: ray_ocache, which takes exactly one argument. The argument should be "disk" or "regenerate".

WARNING: Not all data can be re-generated, meaning that even if all objects are set to the previous behaviour of regeneration of data, the disk cache file may still be constructed and used.

Caching of grid data in mantra has been changed to use a disk cache. The cache will be created (if required) in the houdini tempororary directory (see hconfig HOUDINI_TEMP_DIR) and will be called mcache.XXX, where XXX is a unique identifier for the process being rendered.

When this cache is created, a warning will be output (with verbosity 1 or greater (command line option -V 1)).

The -G option controls the allowed memory before the cache file is created.

Previously, the -G option specified the number of grids to be created. Now, however, it specifies memory allowed. To keep a reasonable form of backwards compatibility, the option specifies a multiple of 4KB chunks of memory. Thus, -G 4096 (the default) allows 16 MB to be used before the disk cache is created.

The previous behaviour of mantra was to re-generate data if it was flushed out of RAM, which could have been prohibitive when expensive shading (such as global illumination) was involved in rendering.

Depending on disk speed (and if the HOUDINI_TEMP_DIR is local or networked), the new caching mechanism may prove to be more expensive than the re-generation of grid data. This behavour can be controlled on a per-object basis using the IFD command: ray_ocache, which takes exactly one argument. The argument should be "disk" or "regenerate".

WARNING: Not all data can be re-generated, meaning that even if all objects are set to the previous behaviour of regeneration of data, the disk cache file may still be constructed and used.

Caching of grid data in mantra has been changed to use a disk cache. The cache will be created (if required) in the houdini tempororary directory (see hconfig HOUDINI_TEMP_DIR) and will be called mcache.XXX, where XXX is a unique identifier for the process being rendered.

When this cache is created, a warning will be output (with verbosity 1 or greater (command line option -V 1)).

The -G option controls the allowed memory before the cache file is created.

Previously, the -G option specified the number of grids to be created. Now, however, it specifies memory allowed. To keep a reasonable form of backwards compatibility, the option specifies a multiple of 4KB chunks of memory. Thus, -G 4096 (the default) allows 16 MB to be used before the disk cache is created.

The previous behaviour of mantra was to re-generate data if it was flushed out of RAM, which could have been prohibitive when expensive shading (such as global illumination) was involved in rendering.

Depending on disk speed (and if the HOUDINI_TEMP_DIR is local or networked), the new caching mechanism may prove to be more expensive than the re-generation of grid data. This behavour can be controlled on a per-object basis using the IFD command: ray_ocache, which takes exactly one argument. The argument should be "disk" or "regenerate".

WARNING: Not all data can be re-generated, meaning that even if all objects are set to the previous behaviour of regeneration of data, the disk cache file may still be constructed and used.

Caching of grid data in mantra has been changed to use a disk cache. The cache will be created (if required) in the houdini tempororary directory (see hconfig HOUDINI_TEMP_DIR) and will be called mcache.XXX, where XXX is a unique identifier for the process being rendered.

When this cache is created, a warning will be output (with verbosity 1 or greater (command line option -V 1)).

The -G option controls the allowed memory before the cache file is created.

Previously, the -G option specified the number of grids to be created. Now, however, it specifies memory allowed. To keep a reasonable form of backwards compatibility, the option specifies a multiple of 4KB chunks of memory. Thus, -G 4096 (the default) allows 16 MB to be used before the disk cache is created.

The previous behaviour of mantra was to re-generate data if it was flushed out of RAM, which could have been prohibitive when expensive shading (such as global illumination) was involved in rendering.

Depending on disk speed (and if the HOUDINI_TEMP_DIR is local or networked), the new caching mechanism may prove to be more expensive than the re-generation of grid data. This behavour can be controlled on a per-object basis using the IFD command: ray_ocache, which takes exactly one argument. The argument should be "disk" or "regenerate".

WARNING: Not all data can be re-generated, meaning that even if all objects are set to the previous behaviour of regeneration of data, the disk cache file may still be constructed and used.

Fixed a crush on mplay startup. This was happening when the a default background has been specified in the preferences and saved as a default to the preference file.