Houdini Main Changelogs
 |
6.1.63 | Fixed a problem where doing a "Create Type From" operation on a COP subnet could cause errors to be introduced inside the subnet, such as inputs becoming disconnected. |
Thu. July 3, 2003 |
|
6.1.63 | Fixed a problem where doing a "Create Type From" operation on a COP subnet could cause errors to be introduced inside the subnet, such as inputs becoming disconnected. |
Thu. July 3, 2003 |
|
6.1.63 | Fixed a problem where doing a "Create Type From" operation on a COP subnet could cause errors to be introduced inside the subnet, such as inputs becoming disconnected. |
Thu. July 3, 2003 |
|
6.1.63 | Fixed a problem where doing a "Create Type From" operation on a COP subnet could cause errors to be introduced inside the subnet, such as inputs becoming disconnected. |
Thu. July 3, 2003 |
 |
6.1.63 | There was a bug in evaluating heavliy attribute laden geometry when displacement mapping. This could have caused core dumps or incorrect evaluation of the attribute data. |
Thu. July 3, 2003 |
|
6.1.63 | There was a bug in evaluating heavliy attribute laden geometry when displacement mapping. This could have caused core dumps or incorrect evaluation of the attribute data. |
Thu. July 3, 2003 |
|
6.1.63 | There was a bug in evaluating heavliy attribute laden geometry when displacement mapping. This could have caused core dumps or incorrect evaluation of the attribute data. |
Thu. July 3, 2003 |
|
6.1.63 | There was a bug in evaluating heavliy attribute laden geometry when displacement mapping. This could have caused core dumps or incorrect evaluation of the attribute data. |
Thu. July 3, 2003 |
|
6.1.63 | There was a bug in evaluating heavliy attribute laden geometry when displacement mapping. This could have caused core dumps or incorrect evaluation of the attribute data. |
Thu. July 3, 2003 |
 |
6.1.63 | The i3dgen application (used by the 3d texture output driver) now uses the standard Houdini instancing code when generating metaball fields for point/particle geometry. This means that metaballs can now be generated with different orientations and scales. Previous .hip files which had the instancing point attributes will now generate different 3d textures. The standard instancing attributes are: v or N - vector (velocity or normal) pscale - 1 float (particle uniform scale) scale - 3 floats (non-uniform scale) up - vector (up direction for orientiation) rot - 4 floats (rotation quaternion) trans - vector (translation offset) orient - 4 floats (orientation quaternion) Note: The "trans" attribute is ignored for metaball creation in i3dgen. |
Thu. July 3, 2003 |
|
6.1.63 | The i3dgen application (used by the 3d texture output driver) now uses the standard Houdini instancing code when generating metaball fields for point/particle geometry. This means that metaballs can now be generated with different orientations and scales. Previous .hip files which had the instancing point attributes will now generate different 3d textures. The standard instancing attributes are: v or N - vector (velocity or normal) pscale - 1 float (particle uniform scale) scale - 3 floats (non-uniform scale) up - vector (up direction for orientiation) rot - 4 floats (rotation quaternion) trans - vector (translation offset) orient - 4 floats (orientation quaternion) Note: The "trans" attribute is ignored for metaball creation in i3dgen. |
Thu. July 3, 2003 |
|
6.1.63 | The i3dgen application (used by the 3d texture output driver) now uses the standard Houdini instancing code when generating metaball fields for point/particle geometry. This means that metaballs can now be generated with different orientations and scales. Previous .hip files which had the instancing point attributes will now generate different 3d textures. The standard instancing attributes are: v or N - vector (velocity or normal) pscale - 1 float (particle uniform scale) scale - 3 floats (non-uniform scale) up - vector (up direction for orientiation) rot - 4 floats (rotation quaternion) trans - vector (translation offset) orient - 4 floats (orientation quaternion) Note: The "trans" attribute is ignored for metaball creation in i3dgen. |
Thu. July 3, 2003 |
|
6.1.63 | The i3dgen application (used by the 3d texture output driver) now uses the standard Houdini instancing code when generating metaball fields for point/particle geometry. This means that metaballs can now be generated with different orientations and scales. Previous .hip files which had the instancing point attributes will now generate different 3d textures. The standard instancing attributes are: v or N - vector (velocity or normal) pscale - 1 float (particle uniform scale) scale - 3 floats (non-uniform scale) up - vector (up direction for orientiation) rot - 4 floats (rotation quaternion) trans - vector (translation offset) orient - 4 floats (orientation quaternion) Note: The "trans" attribute is ignored for metaball creation in i3dgen. |
Thu. July 3, 2003 |
|
6.1.63 | The i3dgen application (used by the 3d texture output driver) now uses the standard Houdini instancing code when generating metaball fields for point/particle geometry. This means that metaballs can now be generated with different orientations and scales. Previous .hip files which had the instancing point attributes will now generate different 3d textures. The standard instancing attributes are: v or N - vector (velocity or normal) pscale - 1 float (particle uniform scale) scale - 3 floats (non-uniform scale) up - vector (up direction for orientiation) rot - 4 floats (rotation quaternion) trans - vector (translation offset) orient - 4 floats (orientation quaternion) Note: The "trans" attribute is ignored for metaball creation in i3dgen. |
Thu. July 3, 2003 |
|
6.1.63 | When i3dgen generates metaballs on point/particle geometry, the standard Houdini instancing code is now used. This means that the metaballs used in i3dgen can now be oriented, scaled, etc. |
Thu. July 3, 2003 |
|
6.1.63 | When i3dgen generates metaballs on point/particle geometry, the standard Houdini instancing code is now used. This means that the metaballs used in i3dgen can now be oriented, scaled, etc. |
Thu. July 3, 2003 |
|
6.1.63 | When i3dgen generates metaballs on point/particle geometry, the standard Houdini instancing code is now used. This means that the metaballs used in i3dgen can now be oriented, scaled, etc. |
Thu. July 3, 2003 |
|
6.1.63 | When i3dgen generates metaballs on point/particle geometry, the standard Houdini instancing code is now used. This means that the metaballs used in i3dgen can now be oriented, scaled, etc. |
Thu. July 3, 2003 |
|
6.1.63 | When i3dgen generates metaballs on point/particle geometry, the standard Houdini instancing code is now used. This means that the metaballs used in i3dgen can now be oriented, scaled, etc. |
Thu. July 3, 2003 |
 |
6.1.63 | Fixed bug in Houdini's command line applications (like mplay) that could sometimes crash on Windows if the supplied command line was too long. For example, typing 'mplay *.jpg' in a directory that contains many files should now only be limited by the command line limit of the user's shell. |
Thu. July 3, 2003 |
|
6.1.63 | Fixed bug in Houdini's command line applications (like mplay) that could sometimes crash on Windows if the supplied command line was too long. For example, typing 'mplay *.jpg' in a directory that contains many files should now only be limited by the command line limit of the user's shell. |
Thu. July 3, 2003 |
|
6.1.63 | Fixed bug in Houdini's command line applications (like mplay) that could sometimes crash on Windows if the supplied command line was too long. For example, typing 'mplay *.jpg' in a directory that contains many files should now only be limited by the command line limit of the user's shell. |
Thu. July 3, 2003 |
|
6.1.63 | Fixed bug in Houdini's command line applications (like mplay) that could sometimes crash on Windows if the supplied command line was too long. For example, typing 'mplay *.jpg' in a directory that contains many files should now only be limited by the command line limit of the user's shell. |
Thu. July 3, 2003 |
|
6.1.63 | Fixed bug in Houdini's command line applications (like mplay) that could sometimes crash on Windows if the supplied command line was too long. For example, typing 'mplay *.jpg' in a directory that contains many files should now only be limited by the command line limit of the user's shell. |
Thu. July 3, 2003 |
|
6.1.63 | Fixed bug in mplay where specifying a frame range on the command line along with the -C option for caching, would ignore the frame range and cache all the available files. Now, only the files in the specified frame range are cached. If the user later decides to change the frame range, the additional files must be loaded explicitly. |
Thu. July 3, 2003 |