The Wood Plank VOP didn't line up the grout between planks with the edge of each plank properly. Now they match up properly. Also fixed a couple of spelling mistakes in operator names.

The "Geometry" field in the render tab of geometry objects has new entries. The entries are as follows:

Geometry as is

• Use geometry from Render SOP as is.

Polygons as Subdivision Surfaces

• Use geometry from Render SOP, but render polys assub-division surfaces. Valid only for Mantra/RenderMan

Render only points

• Use geometry from Render SOP, but render only pointprimitives at each point.

Render from file

• Use geometry from file specified, render as is.

Bounded file (explicit bounds)

• Use geometry from file, but let mantra/RenderMan usedeferred loading of geometry files by specifying thebounding box explicitly.

Bounded file (BBox from render SOP)

• Use geometry from file, but let mantra/RenderMan usedeferred loading of geometry files. Instead of specifyingthe bounding box by hand, let Houdini compute it using thebounding box of the render SOP.

Subdivision from file

• Use geometry from file specified, render polygons assubdivision surfaces. This is only valid for mantra.

Subdivision from file (explicit bounds)

• Use geometry from file, rendering polygons as subdivisionsurfaces. Specify bounding box for deferred loadexplicitly. This is only valid for mantra.

Subdivision from file (render SOP)

• Use geometry from file, rendering polygons as subdivisionsurfaces. Use render SOP to compute bounding box. This isonly valid for mantra.

Points only from file

• Use geometry from file. Render point primitives only. Thisis only valid for mantra.

Points only from file (explicit bounds)

• Use geometry from file, rendering only points. Specifybounding box explicitly for deferred load. Only valid formantra.

Points only from file (render SOP)

• Use geometry from file, rendering only points. Use thebounding box of the render SOP. Only valid for mantra.

The "Geometry" field in the render tab of geometry objects has new entries. The entries are as follows:

Geometry as is

• Use geometry from Render SOP as is.

Polygons as Subdivision Surfaces

• Use geometry from Render SOP, but render polys assub-division surfaces. Valid only for Mantra/RenderMan

Render only points

• Use geometry from Render SOP, but render only pointprimitives at each point.

Render from file

• Use geometry from file specified, render as is.

Bounded file (explicit bounds)

• Use geometry from file, but let mantra/RenderMan usedeferred loading of geometry files by specifying thebounding box explicitly.

Bounded file (BBox from render SOP)

• Use geometry from file, but let mantra/RenderMan usedeferred loading of geometry files. Instead of specifyingthe bounding box by hand, let Houdini compute it using thebounding box of the render SOP.

Subdivision from file

• Use geometry from file specified, render polygons assubdivision surfaces. This is only valid for mantra.

Subdivision from file (explicit bounds)

• Use geometry from file, rendering polygons as subdivisionsurfaces. Specify bounding box for deferred loadexplicitly. This is only valid for mantra.

Subdivision from file (render SOP)

• Use geometry from file, rendering polygons as subdivisionsurfaces. Use render SOP to compute bounding box. This isonly valid for mantra.

Points only from file

• Use geometry from file. Render point primitives only. Thisis only valid for mantra.

Points only from file (explicit bounds)

• Use geometry from file, rendering only points. Specifybounding box explicitly for deferred load. Only valid formantra.

Points only from file (render SOP)

• Use geometry from file, rendering only points. Use thebounding box of the render SOP. Only valid for mantra.

The "Geometry" field in the render tab of geometry objects has new entries. The entries are as follows:

Geometry as is

• Use geometry from Render SOP as is.

Polygons as Subdivision Surfaces

• Use geometry from Render SOP, but render polys assub-division surfaces. Valid only for Mantra/RenderMan

Render only points

• Use geometry from Render SOP, but render only pointprimitives at each point.

Render from file

• Use geometry from file specified, render as is.

Bounded file (explicit bounds)

• Use geometry from file, but let mantra/RenderMan usedeferred loading of geometry files by specifying thebounding box explicitly.

Bounded file (BBox from render SOP)

• Use geometry from file, but let mantra/RenderMan usedeferred loading of geometry files. Instead of specifyingthe bounding box by hand, let Houdini compute it using thebounding box of the render SOP.

Subdivision from file

• Use geometry from file specified, render polygons assubdivision surfaces. This is only valid for mantra.

Subdivision from file (explicit bounds)

• Use geometry from file, rendering polygons as subdivisionsurfaces. Specify bounding box for deferred loadexplicitly. This is only valid for mantra.

Subdivision from file (render SOP)

• Use geometry from file, rendering polygons as subdivisionsurfaces. Use render SOP to compute bounding box. This isonly valid for mantra.

Points only from file

• Use geometry from file. Render point primitives only. Thisis only valid for mantra.

Points only from file (explicit bounds)

• Use geometry from file, rendering only points. Specifybounding box explicitly for deferred load. Only valid formantra.

Points only from file (render SOP)

• Use geometry from file, rendering only points. Use thebounding box of the render SOP. Only valid for mantra.

The "Geometry" field in the render tab of geometry objects has new entries. The entries are as follows:

Geometry as is

• Use geometry from Render SOP as is.

Polygons as Subdivision Surfaces

• Use geometry from Render SOP, but render polys assub-division surfaces. Valid only for Mantra/RenderMan

Render only points

• Use geometry from Render SOP, but render only pointprimitives at each point.

Render from file

• Use geometry from file specified, render as is.

Bounded file (explicit bounds)

• Use geometry from file, but let mantra/RenderMan usedeferred loading of geometry files by specifying thebounding box explicitly.

Bounded file (BBox from render SOP)

• Use geometry from file, but let mantra/RenderMan usedeferred loading of geometry files. Instead of specifyingthe bounding box by hand, let Houdini compute it using thebounding box of the render SOP.

Subdivision from file

• Use geometry from file specified, render polygons assubdivision surfaces. This is only valid for mantra.

Subdivision from file (explicit bounds)

• Use geometry from file, rendering polygons as subdivisionsurfaces. Specify bounding box for deferred loadexplicitly. This is only valid for mantra.

Subdivision from file (render SOP)

• Use geometry from file, rendering polygons as subdivisionsurfaces. Use render SOP to compute bounding box. This isonly valid for mantra.

Points only from file

• Use geometry from file. Render point primitives only. Thisis only valid for mantra.

Points only from file (explicit bounds)

• Use geometry from file, rendering only points. Specifybounding box explicitly for deferred load. Only valid formantra.

Points only from file (render SOP)

• Use geometry from file, rendering only points. Use thebounding box of the render SOP. Only valid for mantra.

The "Geometry" field in the render tab of geometry objects has new entries. The entries are as follows:

Geometry as is

• Use geometry from Render SOP as is.

Polygons as Subdivision Surfaces

• Use geometry from Render SOP, but render polys assub-division surfaces. Valid only for Mantra/RenderMan

Render only points

• Use geometry from Render SOP, but render only pointprimitives at each point.

Render from file

• Use geometry from file specified, render as is.

Bounded file (explicit bounds)

• Use geometry from file, but let mantra/RenderMan usedeferred loading of geometry files by specifying thebounding box explicitly.

Bounded file (BBox from render SOP)

• Use geometry from file, but let mantra/RenderMan usedeferred loading of geometry files. Instead of specifyingthe bounding box by hand, let Houdini compute it using thebounding box of the render SOP.

Subdivision from file

• Use geometry from file specified, render polygons assubdivision surfaces. This is only valid for mantra.

Subdivision from file (explicit bounds)

• Use geometry from file, rendering polygons as subdivisionsurfaces. Specify bounding box for deferred loadexplicitly. This is only valid for mantra.

Subdivision from file (render SOP)

• Use geometry from file, rendering polygons as subdivisionsurfaces. Use render SOP to compute bounding box. This isonly valid for mantra.

Points only from file

• Use geometry from file. Render point primitives only. Thisis only valid for mantra.

Points only from file (explicit bounds)

• Use geometry from file, rendering only points. Specifybounding box explicitly for deferred load. Only valid formantra.

Points only from file (render SOP)

• Use geometry from file, rendering only points. Use thebounding box of the render SOP. Only valid for mantra.

hserver is now able to "hold" licenses after applications are finished with them. Each license type can be held for a different amount of time. When licenses are held, applications can quickly acquire licenses without having to cross the network to a license server. Where there is a slow or busy network, this can improve performance. It is possible to adjust the "hold" time using the -H option on hserver (which will change the hold time on an hserver currently running), or by specifying the hold times in the hserver.opt file.

The heartbeat mechanism for licenses will still be in place for "held" licenses, meaning that if the licenses aren't used, network traffic may be slightly higher than if the licenses weren't held. However, as it's possible to hold licenses for a fixed amount of time (say 1 hour), the network traffic would cease after one hour of disuse (when the licenses would be returned).

Note: For the beta period, don't forget to "hold" Beta licenses along with the other licenses.

There is documentation in the hserver.opt file to show how to hold licenses. Running "hserver -" will give help on how to hold licenses interactively.

hserver is now able to "hold" licenses after applications are finished with them. Each license type can be held for a different amount of time. When licenses are held, applications can quickly acquire licenses without having to cross the network to a license server. Where there is a slow or busy network, this can improve performance. It is possible to adjust the "hold" time using the -H option on hserver (which will change the hold time on an hserver currently running), or by specifying the hold times in the hserver.opt file.

The heartbeat mechanism for licenses will still be in place for "held" licenses, meaning that if the licenses aren't used, network traffic may be slightly higher than if the licenses weren't held. However, as it's possible to hold licenses for a fixed amount of time (say 1 hour), the network traffic would cease after one hour of disuse (when the licenses would be returned).

Note: For the beta period, don't forget to "hold" Beta licenses along with the other licenses.

There is documentation in the hserver.opt file to show how to hold licenses. Running "hserver -" will give help on how to hold licenses interactively.

hserver is now able to "hold" licenses after applications are finished with them. Each license type can be held for a different amount of time. When licenses are held, applications can quickly acquire licenses without having to cross the network to a license server. Where there is a slow or busy network, this can improve performance. It is possible to adjust the "hold" time using the -H option on hserver (which will change the hold time on an hserver currently running), or by specifying the hold times in the hserver.opt file.

The heartbeat mechanism for licenses will still be in place for "held" licenses, meaning that if the licenses aren't used, network traffic may be slightly higher than if the licenses weren't held. However, as it's possible to hold licenses for a fixed amount of time (say 1 hour), the network traffic would cease after one hour of disuse (when the licenses would be returned).

Note: For the beta period, don't forget to "hold" Beta licenses along with the other licenses.

There is documentation in the hserver.opt file to show how to hold licenses. Running "hserver -" will give help on how to hold licenses interactively.

hserver is now able to "hold" licenses after applications are finished with them. Each license type can be held for a different amount of time. When licenses are held, applications can quickly acquire licenses without having to cross the network to a license server. Where there is a slow or busy network, this can improve performance. It is possible to adjust the "hold" time using the -H option on hserver (which will change the hold time on an hserver currently running), or by specifying the hold times in the hserver.opt file.

The heartbeat mechanism for licenses will still be in place for "held" licenses, meaning that if the licenses aren't used, network traffic may be slightly higher than if the licenses weren't held. However, as it's possible to hold licenses for a fixed amount of time (say 1 hour), the network traffic would cease after one hour of disuse (when the licenses would be returned).

Note: For the beta period, don't forget to "hold" Beta licenses along with the other licenses.

There is documentation in the hserver.opt file to show how to hold licenses. Running "hserver -" will give help on how to hold licenses interactively.

hserver is now able to "hold" licenses after applications are finished with them. Each license type can be held for a different amount of time. When licenses are held, applications can quickly acquire licenses without having to cross the network to a license server. Where there is a slow or busy network, this can improve performance. It is possible to adjust the "hold" time using the -H option on hserver (which will change the hold time on an hserver currently running), or by specifying the hold times in the hserver.opt file.

The heartbeat mechanism for licenses will still be in place for "held" licenses, meaning that if the licenses aren't used, network traffic may be slightly higher than if the licenses weren't held. However, as it's possible to hold licenses for a fixed amount of time (say 1 hour), the network traffic would cease after one hour of disuse (when the licenses would be returned).

Note: For the beta period, don't forget to "hold" Beta licenses along with the other licenses.

There is documentation in the hserver.opt file to show how to hold licenses. Running "hserver -" will give help on how to hold licenses interactively.

New Smoke VOP in the Materials toolbar.

New Smoke VOP in the Materials toolbar.

New Smoke VOP in the Materials toolbar.

New Smoke VOP in the Materials toolbar.

New Smoke VOP in the Materials toolbar.

Fixed layout problem with hkey when refreshing an empty window.

Fixed layout problem with hkey when refreshing an empty window.

Fixed layout problem with hkey when refreshing an empty window.

Fixed layout problem with hkey when refreshing an empty window.

Fixed layout problem with hkey when refreshing an empty window.

Middle-clicking on a vop input will now bring up a menu to select whether to create a parameter or a constant vop.

Middle-clicking on a vop input will now bring up a menu to select whether to create a parameter or a constant vop.

Middle-clicking on a vop input will now bring up a menu to select whether to create a parameter or a constant vop.

Middle-clicking on a vop input will now bring up a menu to select whether to create a parameter or a constant vop.