Houdini Main Changelogs
 |
6.5.2 | Fixing a bug where Houdini might crash when copy-stamping geometry where the number of attributes in the stamp changed depending on the copy number. |
Tue. March 2, 2004 |
|
6.5.2 | Fixing a bug where Houdini might crash when copy-stamping geometry where the number of attributes in the stamp changed depending on the copy number. |
Tue. March 2, 2004 |
|
6.5.2 | Fixing a bug where Houdini might crash when copy-stamping geometry where the number of attributes in the stamp changed depending on the copy number. |
Tue. March 2, 2004 |
|
6.5.2 | Fixing a bug where Houdini might crash when copy-stamping geometry where the number of attributes in the stamp changed depending on the copy number. |
Tue. March 2, 2004 |
 |
6.5.2 | In the Operator Type Manager, trying to merge an OTL into the Embedded OTL (when no Embedded OTL currently exists) no longer causes Houdini to crash. |
Tue. March 2, 2004 |
|
6.5.2 | In the Operator Type Manager, trying to merge an OTL into the Embedded OTL (when no Embedded OTL currently exists) no longer causes Houdini to crash. |
Tue. March 2, 2004 |
|
6.5.2 | In the Operator Type Manager, trying to merge an OTL into the Embedded OTL (when no Embedded OTL currently exists) no longer causes Houdini to crash. |
Tue. March 2, 2004 |
|
6.5.2 | In the Operator Type Manager, trying to merge an OTL into the Embedded OTL (when no Embedded OTL currently exists) no longer causes Houdini to crash. |
Tue. March 2, 2004 |
|
6.5.2 | In the Operator Type Manager, trying to merge an OTL into the Embedded OTL (when no Embedded OTL currently exists) no longer causes Houdini to crash. |
Tue. March 2, 2004 |
 |
6.5.1 | The Fetch CHOP now ensures that the order of its created tracks will be in the same order of the parameters within the fetched operator regardless if it is animated. This is then follow by any fetched CHOP data tracks. Previously, the Fetch CHOP created the ordering by channels, chop data tracks, and then non-animated parameters. This behaviour can be obtained by enabling the environment variable HOUDINI6_COMPATIBILITY. |
Mon. March 1, 2004 |
|
6.5.1 | The Fetch CHOP now ensures that the order of its created tracks will be in the same order of the parameters within the fetched operator regardless if it is animated. This is then follow by any fetched CHOP data tracks. Previously, the Fetch CHOP created the ordering by channels, chop data tracks, and then non-animated parameters. This behaviour can be obtained by enabling the environment variable HOUDINI6_COMPATIBILITY. |
Mon. March 1, 2004 |
|
6.5.1 | The Fetch CHOP now ensures that the order of its created tracks will be in the same order of the parameters within the fetched operator regardless if it is animated. This is then follow by any fetched CHOP data tracks. Previously, the Fetch CHOP created the ordering by channels, chop data tracks, and then non-animated parameters. This behaviour can be obtained by enabling the environment variable HOUDINI6_COMPATIBILITY. |
Mon. March 1, 2004 |
|
6.5.1 | The Fetch CHOP now ensures that the order of its created tracks will be in the same order of the parameters within the fetched operator regardless if it is animated. This is then follow by any fetched CHOP data tracks. Previously, the Fetch CHOP created the ordering by channels, chop data tracks, and then non-animated parameters. This behaviour can be obtained by enabling the environment variable HOUDINI6_COMPATIBILITY. |
Mon. March 1, 2004 |
|
6.5.1 | The Fetch CHOP now ensures that the order of its created tracks will be in the same order of the parameters within the fetched operator regardless if it is animated. This is then follow by any fetched CHOP data tracks. Previously, the Fetch CHOP created the ordering by channels, chop data tracks, and then non-animated parameters. This behaviour can be obtained by enabling the environment variable HOUDINI6_COMPATIBILITY. |
Mon. March 1, 2004 |
|
6.5.1 | The Fetch CHOP now ensures that the order of its created tracks will be in the same order of the parameters within the fetched operator regardless if it is animated. This is then follow by any fetched CHOP data tracks. Previously, the Fetch CHOP created the ordering by channels, chop data tracks, and then parameters. This behaviour can be obtained by enabling the environment variable HOUDINI6_COMPATIBILITY. |
Mon. March 1, 2004 |
|
6.5.1 | The Fetch CHOP now ensures that the order of its created tracks will be in the same order of the parameters within the fetched operator regardless if it is animated. This is then follow by any fetched CHOP data tracks. Previously, the Fetch CHOP created the ordering by channels, chop data tracks, and then parameters. This behaviour can be obtained by enabling the environment variable HOUDINI6_COMPATIBILITY. |
Mon. March 1, 2004 |
|
6.5.1 | The Fetch CHOP now ensures that the order of its created tracks will be in the same order of the parameters within the fetched operator regardless if it is animated. This is then follow by any fetched CHOP data tracks. Previously, the Fetch CHOP created the ordering by channels, chop data tracks, and then parameters. This behaviour can be obtained by enabling the environment variable HOUDINI6_COMPATIBILITY. |
Mon. March 1, 2004 |
|
6.5.1 | The Fetch CHOP now ensures that the order of its created tracks will be in the same order of the parameters within the fetched operator regardless if it is animated. This is then follow by any fetched CHOP data tracks. Previously, the Fetch CHOP created the ordering by channels, chop data tracks, and then parameters. This behaviour can be obtained by enabling the environment variable HOUDINI6_COMPATIBILITY. |
Mon. March 1, 2004 |
|
6.5.1 | The Fetch CHOP now ensures that the order of its created tracks will be in the same order of the parameters within the fetched operator regardless if it is animated. This is then follow by any fetched CHOP data tracks. Previously, the Fetch CHOP created the ordering by channels, chop data tracks, and then parameters. This behaviour can be obtained by enabling the environment variable HOUDINI6_COMPATIBILITY. |
Mon. March 1, 2004 |
|
6.5.1 | Houdini now uses pipes (instead of message queues on Linux or shared memory on Windows) to control the help browser. When the help browser runs a Houdini command, though, it still uses message queues. Soon, it will instead use local sockets. |
Mon. March 1, 2004 |
|
6.5.1 | Houdini now uses pipes (instead of message queues on Linux or shared memory on Windows) to control the help browser. When the help browser runs a Houdini command, though, it still uses message queues. Soon, it will instead use local sockets. |
Mon. March 1, 2004 |
|
6.5.1 | Houdini now uses pipes (instead of message queues on Linux or shared memory on Windows) to control the help browser. When the help browser runs a Houdini command, though, it still uses message queues. Soon, it will instead use local sockets. |
Mon. March 1, 2004 |
|
6.5.1 | Houdini now uses pipes (instead of message queues on Linux or shared memory on Windows) to control the help browser. When the help browser runs a Houdini command, though, it still uses message queues. Soon, it will instead use local sockets. |
Mon. March 1, 2004 |
|
6.5.1 | Houdini now uses pipes (instead of message queues on Linux or shared memory on Windows) to control the help browser. When the help browser runs a Houdini command, though, it still uses message queues. Soon, it will instead use local sockets. |
Mon. March 1, 2004 |
 |
6.2.148 | As the title says: Bumped 6.2.150 to 6.5.0 | Fri. February 27, 2004 |