Houdini Main Changelogs
4.9.351 | Added two new options to the SOP viewer menu in an effort to keep visual clutter under control:
Also added (but not implemented) options to delete and hide persistent handles. These options are currently disabled, acting as a reminder for us to implement them. |
Thu. May 3, 2001 | |
4.9.351 | Added two new options to the SOP viewer menu in an effort to keep visual clutter under control:
Also added (but not implemented) options to delete and hide persistent handles. These options are currently disabled, acting as a reminder for us to implement them. |
Thu. May 3, 2001 | |
4.9.351 | When CPP processing was installed in parsing of the VEX Op tables, this broke loading of hip files in hscript. This has been fixed. |
Thu. May 3, 2001 | |
4.9.351 | When CPP processing was installed in parsing of the VEX Op tables, this broke loading of hip files in hscript. This has been fixed. |
Thu. May 3, 2001 | |
4.9.351 | When CPP processing was installed in parsing of the VEX Op tables, this broke loading of hip files in hscript. This has been fixed. |
Thu. May 3, 2001 | |
4.9.351 | When CPP processing was installed in parsing of the VEX Op tables, this broke loading of hip files in hscript. This has been fixed. |
Thu. May 3, 2001 | |
4.9.351 | When CPP processing was installed in parsing of the VEX Op tables, this broke loading of hip files in hscript. This has been fixed. |
Thu. May 3, 2001 | |
4.9.351 | Various fixes to polyknit:
|
Thu. May 3, 2001 | |
4.9.351 | Various fixes to polyknit:
|
Thu. May 3, 2001 | |
4.9.351 | Various fixes to polyknit:
|
Thu. May 3, 2001 | |
4.9.351 | Various fixes to polyknit:
|
Thu. May 3, 2001 | |
4.9.351 | Various fixes to polyknit:
|
Thu. May 3, 2001 | |
4.9.351 | When running hscript command files the execute() function didn't properly grab the output of a sourced command. Now something like: set a = `execute("source foo.cmd")` will work properly inside of a script. |
Thu. May 3, 2001 | |
4.9.351 | When running hscript command files the execute() function didn't properly grab the output of a sourced command. Now something like: set a = `execute("source foo.cmd")` will work properly inside of a script. |
Thu. May 3, 2001 | |
4.9.351 | When running hscript command files the execute() function didn't properly grab the output of a sourced command. Now something like: set a = `execute("source foo.cmd")` will work properly inside of a script. |
Thu. May 3, 2001 | |
4.9.351 | When running hscript command files the execute() function didn't properly grab the output of a sourced command. Now something like: set a = `execute("source foo.cmd")` will work properly inside of a script. |
Thu. May 3, 2001 | |
4.9.351 | When running hscript command files the execute() function didn't properly grab the output of a sourced command. Now something like: set a = `execute("source foo.cmd")` will work properly inside of a script. |
Thu. May 3, 2001 | |
4.9.351 | There was a bug decompressing the first tile in RAT files. This would cause a black square in the bottom left corner to occur when displaying the RAT file. |
Thu. May 3, 2001 | |
4.9.351 | There was a bug decompressing the first tile in RAT files. This would cause a black square in the bottom left corner to occur when displaying the RAT file. |
Thu. May 3, 2001 | |
4.9.351 | There was a bug decompressing the first tile in RAT files. This would cause a black square in the bottom left corner to occur when displaying the RAT file. |
Thu. May 3, 2001 | |
4.9.351 | There was a bug decompressing the first tile in RAT files. This would cause a black square in the bottom left corner to occur when displaying the RAT file. |
Thu. May 3, 2001 | |
4.9.351 | There was a bug decompressing the first tile in RAT files. This would cause a black square in the bottom left corner to occur when displaying the RAT file. |
Thu. May 3, 2001 | |
4.9.350 | Added new sop expression, "xyzdist". This finds the distance to a piece of geometry giving x,y, and z coords. It is just like the pointdist, except you don't need a point. Try it out in the isosurface SOP! Both pointdist and xyzdist are now documented to take "-1" as their primitive number, in which case they will find the closest primitive in the entire SOP rather than a specific one. A new type parameter (3) now allows these functions to return the primitive id of the closest primitive. |
Wed. May 2, 2001 | |
4.9.350 | Added new sop expression, "xyzdist". This finds the distance to a piece of geometry giving x,y, and z coords. It is just like the pointdist, except you don't need a point. Try it out in the isosurface SOP! Both pointdist and xyzdist are now documented to take "-1" as their primitive number, in which case they will find the closest primitive in the entire SOP rather than a specific one. A new type parameter (3) now allows these functions to return the primitive id of the closest primitive. |
Wed. May 2, 2001 | |
4.9.350 | Added new sop expression, "xyzdist". This finds the distance to a piece of geometry giving x,y, and z coords. It is just like the pointdist, except you don't need a point. Try it out in the isosurface SOP! Both pointdist and xyzdist are now documented to take "-1" as their primitive number, in which case they will find the closest primitive in the entire SOP rather than a specific one. A new type parameter (3) now allows these functions to return the primitive id of the closest primitive. |
Wed. May 2, 2001 |