When CPP processing was installed in parsing of the VEX Op tables, this broke loading of hip files in hscript. This has been fixed.

When CPP processing was installed in parsing of the VEX Op tables, this broke loading of hip files in hscript. This has been fixed.

When CPP processing was installed in parsing of the VEX Op tables, this broke loading of hip files in hscript. This has been fixed.

When CPP processing was installed in parsing of the VEX Op tables, this broke loading of hip files in hscript. This has been fixed.

Various fixes to polyknit:

• sop now allows <#> q <#> <#> <#> at the start of the point list tospecify a quadrilateral. This is good since the state wascapable of quite correctly generating these strings.
• state no longer clears the current point list by entering andexitting the state after a strip has been created. This alsois good.

Various fixes to polyknit:

• sop now allows <#> q <#> <#> <#> at the start of the point list tospecify a quadrilateral. This is good since the state wascapable of quite correctly generating these strings.
• state no longer clears the current point list by entering andexitting the state after a strip has been created. This alsois good.

Various fixes to polyknit:

• sop now allows <#> q <#> <#> <#> at the start of the point list tospecify a quadrilateral. This is good since the state wascapable of quite correctly generating these strings.
• state no longer clears the current point list by entering andexitting the state after a strip has been created. This alsois good.

Various fixes to polyknit:

• sop now allows <#> q <#> <#> <#> at the start of the point list tospecify a quadrilateral. This is good since the state wascapable of quite correctly generating these strings.
• state no longer clears the current point list by entering andexitting the state after a strip has been created. This alsois good.

Various fixes to polyknit:

• sop now allows <#> q <#> <#> <#> at the start of the point list tospecify a quadrilateral. This is good since the state wascapable of quite correctly generating these strings.
• state no longer clears the current point list by entering andexitting the state after a strip has been created. This alsois good.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Added checkmarks and a new "Hide" entry to the context-sensitive geometry menu in the SOP viewer (ie the menu accessed with the right mouse button)