Houdini Main Changelogs
 |
6.0.147 | The Group SOP and Delete SOP now behave slightly differently when selecting by normal with a reference normal and spread angle. They now use a small tolerance, so normals which are extremely close to the critical angle, but not quite, are still selected. This was required as floating point errors would often result in a random selection of normals when spread angles of 0, 90, or 180 were chosen with axis aligned geometry. There is no work around for this. |
Thu. December 12, 2002 |
|
6.0.147 | The Group SOP and Delete SOP now behave slightly differently when selecting by normal with a reference normal and spread angle. They now use a small tolerance, so normals which are extremely close to the critical angle, but not quite, are still selected. This was required as floating point errors would often result in a random selection of normals when spread angles of 0, 90, or 180 were chosen with axis aligned geometry. There is no work around for this. |
Thu. December 12, 2002 |
|
6.0.147 | The Group SOP and Delete SOP now behave slightly differently when selecting by normal with a reference normal and spread angle. They now use a small tolerance, so normals which are extremely close to the critical angle, but not quite, are still selected. This was required as floating point errors would often result in a random selection of normals when spread angles of 0, 90, or 180 were chosen with axis aligned geometry. There is no work around for this. |
Thu. December 12, 2002 |
|
6.0.147 | The Group SOP and Delete SOP now behave slightly differently when selecting by normal with a reference normal and spread angle. They now use a small tolerance, so normals which are extremely close to the critical angle, but not quite, are still selected. This was required as floating point errors would often result in a random selection of normals when spread angles of 0, 90, or 180 were chosen with axis aligned geometry. There is no work around for this. |
Thu. December 12, 2002 |
 |
6.0.147 | Optimizations to the composite and layer cops which significantly speed up composites of 8 or 16 bit planes with no transforms (among other criteria). |
Thu. December 12, 2002 |
|
6.0.147 | Optimizations to the composite and layer cops which significantly speed up composites of 8 or 16 bit planes with no transforms (among other criteria). |
Thu. December 12, 2002 |
|
6.0.147 | Optimizations to the composite and layer cops which significantly speed up composites of 8 or 16 bit planes with no transforms (among other criteria). |
Thu. December 12, 2002 |
|
6.0.147 | Optimizations to the composite and layer cops which significantly speed up composites of 8 or 16 bit planes with no transforms (among other criteria). |
Thu. December 12, 2002 |
|
6.0.147 | Optimizations to the composite and layer cops which significantly speed up composites of 8 or 16 bit planes with no transforms (among other criteria). |
Thu. December 12, 2002 |
 |
6.0.147 | Fixed bug where sourcing in scripts that created operators that had local variables in their default parameters would generate spurious errors (but still succeeding). |
Thu. December 12, 2002 |
|
6.0.147 | Fixed bug where sourcing in scripts that created operators that had local variables in their default parameters would generate spurious errors (but still succeeding). |
Thu. December 12, 2002 |
|
6.0.147 | Fixed bug where sourcing in scripts that created operators that had local variables in their default parameters would generate spurious errors (but still succeeding). |
Thu. December 12, 2002 |
|
6.0.147 | Fixed bug where sourcing in scripts that created operators that had local variables in their default parameters would generate spurious errors (but still succeeding). |
Thu. December 12, 2002 |
|
6.0.147 | Fixed bug where sourcing in scripts that created operators that had local variables in their default parameters would generate spurious errors (but still succeeding). |
Thu. December 12, 2002 |
|
6.0.146 | The help for the -m option of the opscript command has now been fixed. The actual syntax for the -m option is "-m in_wire out_wire" where in_wire is the input wire node path and out_wire is the output wire node path. Also documented the -o option of the opscript command. |
Wed. December 11, 2002 |
|
6.0.146 | The help for the -m option of the opscript command has now been fixed. The actual syntax for the -m option is "-m in_wire out_wire" where in_wire is the input wire node path and out_wire is the output wire node path. Also documented the -o option of the opscript command. |
Wed. December 11, 2002 |
|
6.0.146 | The help for the -m option of the opscript command has now been fixed. The actual syntax for the -m option is "-m in_wire out_wire" where in_wire is the input wire node path and out_wire is the output wire node path. Also documented the -o option of the opscript command. |
Wed. December 11, 2002 |
|
6.0.146 | The help for the -m option of the opscript command has now been fixed. The actual syntax for the -m option is "-m in_wire out_wire" where in_wire is the input wire node path and out_wire is the output wire node path. Also documented the -o option of the opscript command. |
Wed. December 11, 2002 |
|
6.0.146 | The help for the -m option of the opscript command has now been fixed. The actual syntax for the -m option is "-m in_wire out_wire" where in_wire is the input wire node path and out_wire is the output wire node path. Also documented the -o option of the opscript command. |
Wed. December 11, 2002 |
|
6.0.146 | Fixed bug where if you specified "file`opdigits(".")`.$F4.rla" in the output picture parameter of an output driver, then changing its name would change the parameter to "file`opdigits(".")`..rla". Specifically, it used try expand any variable references with the current environment. |
Wed. December 11, 2002 |
|
6.0.146 | Fixed bug where if you specified "file`opdigits(".")`.$F4.rla" in the output picture parameter of an output driver, then changing its name would change the parameter to "file`opdigits(".")`..rla". Specifically, it used try expand any variable references with the current environment. |
Wed. December 11, 2002 |
|
6.0.146 | Fixed bug where if you specified "file`opdigits(".")`.$F4.rla" in the output picture parameter of an output driver, then changing its name would change the parameter to "file`opdigits(".")`..rla". Specifically, it used try expand any variable references with the current environment. |
Wed. December 11, 2002 |
|
6.0.146 | Fixed bug where if you specified "file`opdigits(".")`.$F4.rla" in the output picture parameter of an output driver, then changing its name would change the parameter to "file`opdigits(".")`..rla". Specifically, it used try expand any variable references with the current environment. |
Wed. December 11, 2002 |
|
6.0.146 | Fixed bug where if you specified "file`opdigits(".")`.$F4.rla" in the output picture parameter of an output driver, then changing its name would change the parameter to "file`opdigits(".")`..rla". Specifically, it used try expand any variable references with the current environment. |
Wed. December 11, 2002 |
 |
6.0.146 | OP_Node::getHelpText now has an additional parameter. The new prototype is: virtual void getHelpText(UT_String &str, int level = 0, bool *is_html_ptr = 0); If is_html_ptr is not null, the bool should be set to indicate whether or not the help is in html. |
Wed. December 11, 2002 |