Houdini Main Changelogs

7.0.163

Handling of the "scope" argument in shaders has very slight different symantics now. Previously, if an invalid pattern was specified (i.e. the pattern referred to a non-existant object), the pattern was assumed to be invalid and mantra defaulted to the object's reflection mask (or the appropriate mask). Now, an invalid mask will be interpreted as a mask which will not intersect any objects, which is a more correct interpretation.

Wed. August 18, 2004
7.0.163

Handling of the "scope" argument in shaders has very slight different symantics now. Previously, if an invalid pattern was specified (i.e. the pattern referred to a non-existant object), the pattern was assumed to be invalid and mantra defaulted to the object's reflection mask (or the appropriate mask). Now, an invalid mask will be interpreted as a mask which will not intersect any objects, which is a more correct interpretation.

Wed. August 18, 2004
7.0.163

Handling of the "scope" argument in shaders has very slight different symantics now. Previously, if an invalid pattern was specified (i.e. the pattern referred to a non-existant object), the pattern was assumed to be invalid and mantra defaulted to the object's reflection mask (or the appropriate mask). Now, an invalid mask will be interpreted as a mask which will not intersect any objects, which is a more correct interpretation.

Wed. August 18, 2004
7.0.163

Handling of the "scope" argument in shaders has very slight different symantics now. Previously, if an invalid pattern was specified (i.e. the pattern referred to a non-existant object), the pattern was assumed to be invalid and mantra defaulted to the object's reflection mask (or the appropriate mask). Now, an invalid mask will be interpreted as a mask which will not intersect any objects, which is a more correct interpretation.

Wed. August 18, 2004
7.0.163

The system() expression function (and the systemES() function) now handle back-slash protected double quotes slightly differently. This enables functions like: system("echo \"This is a test\" | grep \"test\"") to be evaluated properly.

Wed. August 18, 2004
7.0.163

The system() expression function (and the systemES() function) now handle back-slash protected double quotes slightly differently. This enables functions like: system("echo \"This is a test\" | grep \"test\"") to be evaluated properly.

Wed. August 18, 2004
7.0.163

The system() expression function (and the systemES() function) now handle back-slash protected double quotes slightly differently. This enables functions like: system("echo \"This is a test\" | grep \"test\"") to be evaluated properly.

Wed. August 18, 2004
7.0.163

The system() expression function (and the systemES() function) now handle back-slash protected double quotes slightly differently. This enables functions like: system("echo \"This is a test\" | grep \"test\"") to be evaluated properly.

Wed. August 18, 2004
7.0.163

The system() expression function (and the systemES() function) now handle back-slash protected double quotes slightly differently. This enables functions like: system("echo \"This is a test\" | grep \"test\"") to be evaluated properly.

Wed. August 18, 2004
7.0.163

rscript should work as advertised now.

Wed. August 18, 2004
7.0.163

rscript should work as advertised now.

Wed. August 18, 2004
7.0.163

rscript should work as advertised now.

Wed. August 18, 2004
7.0.163

rscript should work as advertised now.

Wed. August 18, 2004
7.0.163

rscript should work as advertised now.

Wed. August 18, 2004
7.0.163

Changing the autoscope behaviour so that it always matches which nodes are currently selected. Before, when a node became selected it would add the parameters to the scope and when it was deselected it would remove the parameters from the scope. Unfortunately, if other parameters were scoped outside of autoscoping, they wouldn't be unscoped when the selection changed.

Wed. August 18, 2004
7.0.163

Changing the autoscope behaviour so that it always matches which nodes are currently selected. Before, when a node became selected it would add the parameters to the scope and when it was deselected it would remove the parameters from the scope. Unfortunately, if other parameters were scoped outside of autoscoping, they wouldn't be unscoped when the selection changed.

Wed. August 18, 2004
7.0.163

Changing the autoscope behaviour so that it always matches which nodes are currently selected. Before, when a node became selected it would add the parameters to the scope and when it was deselected it would remove the parameters from the scope. Unfortunately, if other parameters were scoped outside of autoscoping, they wouldn't be unscoped when the selection changed.

Wed. August 18, 2004
7.0.163

Changing the autoscope behaviour so that it always matches which nodes are currently selected. Before, when a node became selected it would add the parameters to the scope and when it was deselected it would remove the parameters from the scope. Unfortunately, if other parameters were scoped outside of autoscoping, they wouldn't be unscoped when the selection changed.

Wed. August 18, 2004
7.0.163

Changing the autoscope behaviour so that it always matches which nodes are currently selected. Before, when a node became selected it would add the parameters to the scope and when it was deselected it would remove the parameters from the scope. Unfortunately, if other parameters were scoped outside of autoscoping, they wouldn't be unscoped when the selection changed.

Wed. August 18, 2004
7.0.163

Fixed openport -a to always return the correct port number that it opened. It might have been off by 10000 if the process pid was less than 10000.

Wed. August 18, 2004
7.0.163

Fixed openport -a to always return the correct port number that it opened. It might have been off by 10000 if the process pid was less than 10000.

Wed. August 18, 2004
7.0.163

Fixed openport -a to always return the correct port number that it opened. It might have been off by 10000 if the process pid was less than 10000.

Wed. August 18, 2004
7.0.163

Fixed openport -a to always return the correct port number that it opened. It might have been off by 10000 if the process pid was less than 10000.

Wed. August 18, 2004
7.0.163

Fixed openport -a to always return the correct port number that it opened. It might have been off by 10000 if the process pid was less than 10000.

Wed. August 18, 2004
7.0.162

Fixed bug where non-sequence renders from the Viewport Render Button would not be backgrounded if the corresponding ROP had its frame range enabled.

Tue. August 17, 2004