Houdini Main Changelogs
 |
9.0.285 | Fixed a bug where some images in the UI would appear flipped. In particular, the background in the 3D viewport and the background image in the network editor. |
Thu. July 6, 2006 |
|
9.0.285 | Fixed a bug where some images in the UI would appear flipped. In particular, the background in the 3D viewport and the background image in the network editor. |
Thu. July 6, 2006 |
|
9.0.285 | Fixed a bug where some images in the UI would appear flipped. In particular, the background in the 3D viewport and the background image in the network editor. |
Thu. July 6, 2006 |
|
9.0.285 | Fixed a bug where some images in the UI would appear flipped. In particular, the background in the 3D viewport and the background image in the network editor. |
Thu. July 6, 2006 |
 |
9.0.285 | The Muscle Object and SOP no longer assume that the profile curves (defined via channels) are 100 frames in length. It now uses their actual time length to figure out how to scale each metaball. The color gradient was also changed to use this method. |
Thu. July 6, 2006 |
|
9.0.285 | The Muscle Object and SOP no longer assume that the profile curves (defined via channels) are 100 frames in length. It now uses their actual time length to figure out how to scale each metaball. The color gradient was also changed to use this method. |
Thu. July 6, 2006 |
|
9.0.285 | The Muscle Object and SOP no longer assume that the profile curves (defined via channels) are 100 frames in length. It now uses their actual time length to figure out how to scale each metaball. The color gradient was also changed to use this method. |
Thu. July 6, 2006 |
|
9.0.285 | The Muscle Object and SOP no longer assume that the profile curves (defined via channels) are 100 frames in length. It now uses their actual time length to figure out how to scale each metaball. The color gradient was also changed to use this method. |
Thu. July 6, 2006 |
|
9.0.285 | The Muscle Object and SOP no longer assume that the profile curves (defined via channels) are 100 frames in length. It now uses their actual time length to figure out how to scale each metaball. The color gradient was also changed to use this method. |
Thu. July 6, 2006 |
 |
9.0.285 | Fixed potential crash that sometimes would occur when quitting mplay. |
Thu. July 6, 2006 |
|
9.0.285 | Fixed potential crash that sometimes would occur when quitting mplay. |
Thu. July 6, 2006 |
|
9.0.285 | Fixed potential crash that sometimes would occur when quitting mplay. |
Thu. July 6, 2006 |
|
9.0.285 | Fixed potential crash that sometimes would occur when quitting mplay. |
Thu. July 6, 2006 |
|
9.0.285 | Fixed potential crash that sometimes would occur when quitting mplay. |
Thu. July 6, 2006 |
|
9.0.284 | The Edit SOP uses a new interface for local coordinate frames. HDK users need to use the getCoordinateFrames() method instead of directly accessing a member variable. Also, the methods on GDT_CoordinateFrames have been modified to allow coordinate frames to be described by arbitary 3x3 matrices. HDK users will need to convert all coordinate frame descriptions to 3x3 matrices to continue using the GDT_CoordinateFrames class. |
Wed. July 5, 2006 |
|
9.0.284 | The Edit SOP uses a new interface for local coordinate frames. HDK users need to use the getCoordinateFrames() method instead of directly accessing a member variable. Also, the methods on GDT_CoordinateFrames have been modified to allow coordinate frames to be described by arbitary 3x3 matrices. HDK users will need to convert all coordinate frame descriptions to 3x3 matrices to continue using the GDT_CoordinateFrames class. |
Wed. July 5, 2006 |
|
9.0.284 | The Edit SOP uses a new interface for local coordinate frames. HDK users need to use the getCoordinateFrames() method instead of directly accessing a member variable. Also, the methods on GDT_CoordinateFrames have been modified to allow coordinate frames to be described by arbitary 3x3 matrices. HDK users will need to convert all coordinate frame descriptions to 3x3 matrices to continue using the GDT_CoordinateFrames class. |
Wed. July 5, 2006 |
|
9.0.284 | The Edit SOP uses a new interface for local coordinate frames. HDK users need to use the getCoordinateFrames() method instead of directly accessing a member variable. Also, the methods on GDT_CoordinateFrames have been modified to allow coordinate frames to be described by arbitary 3x3 matrices. HDK users will need to convert all coordinate frame descriptions to 3x3 matrices to continue using the GDT_CoordinateFrames class. |
Wed. July 5, 2006 |
|
9.0.284 | The Edit SOP uses a new interface for local coordinate frames. HDK users need to use the getCoordinateFrames() method instead of directly accessing a member variable. Also, the methods on GDT_CoordinateFrames have been modified to allow coordinate frames to be described by arbitary 3x3 matrices. HDK users will need to convert all coordinate frame descriptions to 3x3 matrices to continue using the GDT_CoordinateFrames class. |
Wed. July 5, 2006 |
|
9.0.284 | The Edit SOP now exposes methods that let HDK users modify the local coordinate frames used to apply relative edits. |
Wed. July 5, 2006 |
|
9.0.284 | The Edit SOP now exposes methods that let HDK users modify the local coordinate frames used to apply relative edits. |
Wed. July 5, 2006 |
|
9.0.284 | The Edit SOP now exposes methods that let HDK users modify the local coordinate frames used to apply relative edits. |
Wed. July 5, 2006 |
|
9.0.284 | The Edit SOP now exposes methods that let HDK users modify the local coordinate frames used to apply relative edits. |
Wed. July 5, 2006 |
|
9.0.284 | The Edit SOP now exposes methods that let HDK users modify the local coordinate frames used to apply relative edits. |
Wed. July 5, 2006 |
|
9.0.283 | Added a scale profiles option for the Muscle Object and Muscle SOP. This scales all the profiles defined for the muscle by the amount specified. |
Tue. July 4, 2006 |