Houdini Main Changelogs
 |
5.1.66 | We now have rounded connectors for tiles. |
Thu. March 28, 2002 |
|
5.1.66 | We now have rounded connectors for tiles. |
Thu. March 28, 2002 |
|
5.1.66 | We now have rounded connectors for tiles. |
Thu. March 28, 2002 |
|
5.1.66 | Fixing the saving of handle binding default settings strings. |
Thu. March 28, 2002 |
|
5.1.66 | Fixing the saving of handle binding default settings strings. |
Thu. March 28, 2002 |
|
5.1.66 | Fixing the saving of handle binding default settings strings. |
Thu. March 28, 2002 |
|
5.1.66 | Fixing the saving of handle binding default settings strings. |
Thu. March 28, 2002 |
|
5.1.66 | Fixing the saving of handle binding default settings strings. |
Thu. March 28, 2002 |
|
5.1.65 | There's a new environment variable HOUDINI_MPLAY_LOCKPATH which determines where the mplay .lockfiles are put. This allows users with home directories on NFS to avoid the network penalties by setting the lock file to a local path (i.e. /tmp or c:/temp). |
Wed. March 27, 2002 |
|
5.1.65 | There's a new environment variable HOUDINI_MPLAY_LOCKPATH which determines where the mplay .lockfiles are put. This allows users with home directories on NFS to avoid the network penalties by setting the lock file to a local path (i.e. /tmp or c:/temp). |
Wed. March 27, 2002 |
|
5.1.65 | There's a new environment variable HOUDINI_MPLAY_LOCKPATH which determines where the mplay .lockfiles are put. This allows users with home directories on NFS to avoid the network penalties by setting the lock file to a local path (i.e. /tmp or c:/temp). |
Wed. March 27, 2002 |
|
5.1.65 | There's a new environment variable HOUDINI_MPLAY_LOCKPATH which determines where the mplay .lockfiles are put. This allows users with home directories on NFS to avoid the network penalties by setting the lock file to a local path (i.e. /tmp or c:/temp). |
Wed. March 27, 2002 |
|
5.1.65 | There's a new environment variable HOUDINI_MPLAY_LOCKPATH which determines where the mplay .lockfiles are put. This allows users with home directories on NFS to avoid the network penalties by setting the lock file to a local path (i.e. /tmp or c:/temp). |
Wed. March 27, 2002 |
|
5.1.64 | vcc has been modified to recognize 3.0f or 3.0F as a floating point constant (in accordance to the ANSI mechanism for specifying storage). The ANSI extensions "i", "I", "l" and "L" are not supported. Thus 3i or 3l will still generate syntax errors. |
Tue. March 26, 2002 |
|
5.1.64 | vcc has been modified to recognize 3.0f or 3.0F as a floating point constant (in accordance to the ANSI mechanism for specifying storage). The ANSI extensions "i", "I", "l" and "L" are not supported. Thus 3i or 3l will still generate syntax errors. |
Tue. March 26, 2002 |
|
5.1.64 | vcc has been modified to recognize 3.0f or 3.0F as a floating point constant (in accordance to the ANSI mechanism for specifying storage). The ANSI extensions "i", "I", "l" and "L" are not supported. Thus 3i or 3l will still generate syntax errors. |
Tue. March 26, 2002 |
|
5.1.64 | vcc has been modified to recognize 3.0f or 3.0F as a floating point constant (in accordance to the ANSI mechanism for specifying storage). The ANSI extensions "i", "I", "l" and "L" are not supported. Thus 3i or 3l will still generate syntax errors. |
Tue. March 26, 2002 |
|
5.1.64 | vcc has been modified to recognize 3.0f or 3.0F as a floating point constant (in accordance to the ANSI mechanism for specifying storage). The ANSI extensions "i", "I", "l" and "L" are not supported. Thus 3i or 3l will still generate syntax errors. |
Tue. March 26, 2002 |
 |
5.1.64 | Output of metaballs to RIB was changed drastically. Due to a mis-interpretation of the metaball spec, the metaball weight was effectively output as a scale on the metaball (which is incorrect). Now, the weight is ignored in metaball output unless it's negative (in which case the metaball is subtracted from the sum of the positive metaballs). |
Tue. March 26, 2002 |
|
5.1.64 | Output of metaballs to RIB was changed drastically. Due to a mis-interpretation of the metaball spec, the metaball weight was effectively output as a scale on the metaball (which is incorrect). Now, the weight is ignored in metaball output unless it's negative (in which case the metaball is subtracted from the sum of the positive metaballs). |
Tue. March 26, 2002 |
|
5.1.64 | Output of metaballs to RIB was changed drastically. Due to a mis-interpretation of the metaball spec, the metaball weight was effectively output as a scale on the metaball (which is incorrect). Now, the weight is ignored in metaball output unless it's negative (in which case the metaball is subtracted from the sum of the positive metaballs). |
Tue. March 26, 2002 |
|
5.1.64 | Output of metaballs to RIB was changed drastically. Due to a mis-interpretation of the metaball spec, the metaball weight was effectively output as a scale on the metaball (which is incorrect). Now, the weight is ignored in metaball output unless it's negative (in which case the metaball is subtracted from the sum of the positive metaballs). |
Tue. March 26, 2002 |
|
5.1.64 | Output of metaballs to RIB was changed drastically. Due to a mis-interpretation of the metaball spec, the metaball weight was effectively output as a scale on the metaball (which is incorrect). Now, the weight is ignored in metaball output unless it's negative (in which case the metaball is subtracted from the sum of the positive metaballs). |
Tue. March 26, 2002 |
|
5.1.64 | Computation of normals for metaballs was "fixed". The previous version caused artifacting of metaball normals. Metaballs will be rendered much smoother now in mantra. |
Tue. March 26, 2002 |
|
5.1.64 | Computation of normals for metaballs was "fixed". The previous version caused artifacting of metaball normals. Metaballs will be rendered much smoother now in mantra. |
Tue. March 26, 2002 |