Houdini Main Changelogs

6.0.138

The new POP Network SOP, introduced with the Networks-Within-Networks changes, is now improved. It now is a true SOP with four inputs and an output. These do the equivalent of having a seperate Pop Merge SOP that references the POP Network sop.

Tue. December 3, 2002
6.0.138

The new POP Network SOP, introduced with the Networks-Within-Networks changes, is now improved. It now is a true SOP with four inputs and an output. These do the equivalent of having a seperate Pop Merge SOP that references the POP Network sop.

Tue. December 3, 2002
6.0.138

The new POP Network SOP, introduced with the Networks-Within-Networks changes, is now improved. It now is a true SOP with four inputs and an output. These do the equivalent of having a seperate Pop Merge SOP that references the POP Network sop.

Tue. December 3, 2002
6.0.138

The new POP Network SOP, introduced with the Networks-Within-Networks changes, is now improved. It now is a true SOP with four inputs and an output. These do the equivalent of having a seperate Pop Merge SOP that references the POP Network sop.

Tue. December 3, 2002
6.0.138

The isixpack tool has new options available. It is now possible to take a single image which contains sub-images representing the different faces of a cubic environment map and use this as a source image instead of having to provide six individual images. Also, it is possible to take a cubic environment .rat file and convert it into a single image containing each face as a sub-image. Floating point cubic .rat files should also work properly now. This allows HDR images to be converted into a format which allows mantra/houdini to efficiently access them.

Tue. December 3, 2002
6.0.138

The isixpack tool has new options available. It is now possible to take a single image which contains sub-images representing the different faces of a cubic environment map and use this as a source image instead of having to provide six individual images. Also, it is possible to take a cubic environment .rat file and convert it into a single image containing each face as a sub-image. Floating point cubic .rat files should also work properly now. This allows HDR images to be converted into a format which allows mantra/houdini to efficiently access them.

Tue. December 3, 2002
6.0.138

The isixpack tool has new options available. It is now possible to take a single image which contains sub-images representing the different faces of a cubic environment map and use this as a source image instead of having to provide six individual images. Also, it is possible to take a cubic environment .rat file and convert it into a single image containing each face as a sub-image. Floating point cubic .rat files should also work properly now. This allows HDR images to be converted into a format which allows mantra/houdini to efficiently access them.

Tue. December 3, 2002
6.0.138

The isixpack tool has new options available. It is now possible to take a single image which contains sub-images representing the different faces of a cubic environment map and use this as a source image instead of having to provide six individual images. Also, it is possible to take a cubic environment .rat file and convert it into a single image containing each face as a sub-image. Floating point cubic .rat files should also work properly now. This allows HDR images to be converted into a format which allows mantra/houdini to efficiently access them.

Tue. December 3, 2002
6.0.138

The isixpack tool has new options available. It is now possible to take a single image which contains sub-images representing the different faces of a cubic environment map and use this as a source image instead of having to provide six individual images. Also, it is possible to take a cubic environment .rat file and convert it into a single image containing each face as a sub-image. Floating point cubic .rat files should also work properly now. This allows HDR images to be converted into a format which allows mantra/houdini to efficiently access them.

Tue. December 3, 2002
6.0.138

Houdini now has support for RADIANCE rgbe encoded images. These provide lossy floating point compression for RGB images and are often used for HDR Images (see: http://www.debevec.org/Probes/).

Tue. December 3, 2002
6.0.138

Houdini now has support for RADIANCE rgbe encoded images. These provide lossy floating point compression for RGB images and are often used for HDR Images (see: http://www.debevec.org/Probes/).

Tue. December 3, 2002
6.0.138

Houdini now has support for RADIANCE rgbe encoded images. These provide lossy floating point compression for RGB images and are often used for HDR Images (see: http://www.debevec.org/Probes/).

Tue. December 3, 2002
6.0.138

Houdini now has support for RADIANCE rgbe encoded images. These provide lossy floating point compression for RGB images and are often used for HDR Images (see: http://www.debevec.org/Probes/).

Tue. December 3, 2002
6.0.138

Houdini now has support for RADIANCE rgbe encoded images. These provide lossy floating point compression for RGB images and are often used for HDR Images (see: http://www.debevec.org/Probes/).

Tue. December 3, 2002
6.0.137

The old attribute ATT_POSOBJ and ATT_POSSOP, known as "posobj", and "possop", are now replaced by a single attribute ATT_POSPATH, or "pospath". This forms the complete path to the referenced SOP rather than having the path broken up into an object and sop component. This matches the UI changes where the seperate Object and Sop menus have been combined into a single string.

Older files should convert with no problems as their relevant UI will change appropriately, but custom POPs which rely on these attributes will have to be updated. Note that given a SOP_Node *, one can always get the OBJ_Node * that contains it with the getCreator() function.

Mon. December 2, 2002
6.0.137

The old attribute ATT_POSOBJ and ATT_POSSOP, known as "posobj", and "possop", are now replaced by a single attribute ATT_POSPATH, or "pospath". This forms the complete path to the referenced SOP rather than having the path broken up into an object and sop component. This matches the UI changes where the seperate Object and Sop menus have been combined into a single string.

Older files should convert with no problems as their relevant UI will change appropriately, but custom POPs which rely on these attributes will have to be updated. Note that given a SOP_Node *, one can always get the OBJ_Node * that contains it with the getCreator() function.

Mon. December 2, 2002
6.0.137

The old attribute ATT_POSOBJ and ATT_POSSOP, known as "posobj", and "possop", are now replaced by a single attribute ATT_POSPATH, or "pospath". This forms the complete path to the referenced SOP rather than having the path broken up into an object and sop component. This matches the UI changes where the seperate Object and Sop menus have been combined into a single string.

Older files should convert with no problems as their relevant UI will change appropriately, but custom POPs which rely on these attributes will have to be updated. Note that given a SOP_Node *, one can always get the OBJ_Node * that contains it with the getCreator() function.

Mon. December 2, 2002
6.0.137

The old attribute ATT_POSOBJ and ATT_POSSOP, known as "posobj", and "possop", are now replaced by a single attribute ATT_POSPATH, or "pospath". This forms the complete path to the referenced SOP rather than having the path broken up into an object and sop component. This matches the UI changes where the seperate Object and Sop menus have been combined into a single string.

Older files should convert with no problems as their relevant UI will change appropriately, but custom POPs which rely on these attributes will have to be updated. Note that given a SOP_Node *, one can always get the OBJ_Node * that contains it with the getCreator() function.

Mon. December 2, 2002
6.0.137

The old attribute ATT_POSOBJ and ATT_POSSOP, known as "posobj", and "possop", are now replaced by a single attribute ATT_POSPATH, or "pospath". This forms the complete path to the referenced SOP rather than having the path broken up into an object and sop component. This matches the UI changes where the seperate Object and Sop menus have been combined into a single string.

Older files should convert with no problems as their relevant UI will change appropriately, but custom POPs which rely on these attributes will have to be updated. Note that given a SOP_Node *, one can always get the OBJ_Node * that contains it with the getCreator() function.

Mon. December 2, 2002
6.0.137

There are now separate controls for limiting reflection vs. refraction ray-bounces.

Mon. December 2, 2002
6.0.137

There are now separate controls for limiting reflection vs. refraction ray-bounces.

Mon. December 2, 2002
6.0.137

There are now separate controls for limiting reflection vs. refraction ray-bounces.

Mon. December 2, 2002
6.0.137

There are now separate controls for limiting reflection vs. refraction ray-bounces.

Mon. December 2, 2002
6.0.137

There are now separate controls for limiting reflection vs. refraction ray-bounces.

Mon. December 2, 2002
6.0.135

Added per-point feathering widths to the rotospline, as well as the handles for manipulating them.

Sat. November 30, 2002