Houdini Main Changelogs
6.0.214 | Fixed a problem where selecting "Edit Comment" from the comment button in a operator dialog would sometimes bring up several comment windows, each for a different operator. |
Mon. February 17, 2003 | |
6.0.214 | Fixed a problem where selecting "Edit Comment" from the comment button in a operator dialog would sometimes bring up several comment windows, each for a different operator. |
Mon. February 17, 2003 | |
6.0.214 | Fixed a problem where selecting "Edit Comment" from the comment button in a operator dialog would sometimes bring up several comment windows, each for a different operator. |
Mon. February 17, 2003 | |
6.0.214 | Fixed a problem where selecting "Edit Comment" from the comment button in a operator dialog would sometimes bring up several comment windows, each for a different operator. |
Mon. February 17, 2003 | |
6.0.214 | Fixed a problem where selecting "Edit Comment" from the comment button in a operator dialog would sometimes bring up several comment windows, each for a different operator. |
Mon. February 17, 2003 | |
6.0.214 | On the Handles page of the Type Properties dialog, the standard Transform parameters are now listed as possible bindings for Object subnet types. |
Mon. February 17, 2003 | |
6.0.214 | On the Handles page of the Type Properties dialog, the standard Transform parameters are now listed as possible bindings for Object subnet types. |
Mon. February 17, 2003 | |
6.0.214 | On the Handles page of the Type Properties dialog, the standard Transform parameters are now listed as possible bindings for Object subnet types. |
Mon. February 17, 2003 | |
6.0.214 | On the Handles page of the Type Properties dialog, the standard Transform parameters are now listed as possible bindings for Object subnet types. |
Mon. February 17, 2003 | |
6.0.214 | On the Handles page of the Type Properties dialog, the standard Transform parameters are now listed as possible bindings for Object subnet types. |
Mon. February 17, 2003 | |
6.0.214 | Fixing a problem where the split, copy, tear off, and move playbar here entries in the pane menu bars weren't disabled when they should be. |
Mon. February 17, 2003 | |
6.0.214 | Fixing a problem where the split, copy, tear off, and move playbar here entries in the pane menu bars weren't disabled when they should be. |
Mon. February 17, 2003 | |
6.0.214 | Fixing a problem where the split, copy, tear off, and move playbar here entries in the pane menu bars weren't disabled when they should be. |
Mon. February 17, 2003 | |
6.0.214 | Fixing a problem where the split, copy, tear off, and move playbar here entries in the pane menu bars weren't disabled when they should be. |
Mon. February 17, 2003 | |
6.0.214 | Fixing a problem where the split, copy, tear off, and move playbar here entries in the pane menu bars weren't disabled when they should be. |
Mon. February 17, 2003 | |
6.0.214 | Houdini now requires version 6 licenses to run. It now also requires an additional beta license. |
Mon. February 17, 2003 | |
6.0.214 | Houdini now requires version 6 licenses to run. It now also requires an additional beta license. |
Mon. February 17, 2003 | |
6.0.214 | Houdini now requires version 6 licenses to run. It now also requires an additional beta license. |
Mon. February 17, 2003 | |
6.0.214 | Houdini now requires version 6 licenses to run. It now also requires an additional beta license. |
Mon. February 17, 2003 | |
6.0.214 | Houdini now requires version 6 licenses to run. It now also requires an additional beta license. |
Mon. February 17, 2003 | |
6.0.214 | When instancing geometry (or lights), orientation is now more consistent with the copy SOP. Rotating the orientation now works as follows: 1) If the normal attribute exists, use this to define the orientation. 2) If the normal attribute doesn't exist, but the velocity attribute does, then use the velocity attribute for orientation. 3) If neither the normal or the velocity attributes exist, then don't perform any orientation. One major difference is that the Copy SOP will automatically compute normals before step 3 is taken. This is not automatically done when instancing for rendering. |
Mon. February 17, 2003 | |
6.0.214 | When instancing geometry (or lights), orientation is now more consistent with the copy SOP. Rotating the orientation now works as follows: 1) If the normal attribute exists, use this to define the orientation. 2) If the normal attribute doesn't exist, but the velocity attribute does, then use the velocity attribute for orientation. 3) If neither the normal or the velocity attributes exist, then don't perform any orientation. One major difference is that the Copy SOP will automatically compute normals before step 3 is taken. This is not automatically done when instancing for rendering. |
Mon. February 17, 2003 | |
6.0.214 | When instancing geometry (or lights), orientation is now more consistent with the copy SOP. Rotating the orientation now works as follows: 1) If the normal attribute exists, use this to define the orientation. 2) If the normal attribute doesn't exist, but the velocity attribute does, then use the velocity attribute for orientation. 3) If neither the normal or the velocity attributes exist, then don't perform any orientation. One major difference is that the Copy SOP will automatically compute normals before step 3 is taken. This is not automatically done when instancing for rendering. |
Mon. February 17, 2003 | |
6.0.214 | When instancing geometry (or lights), orientation is now more consistent with the copy SOP. Rotating the orientation now works as follows: 1) If the normal attribute exists, use this to define the orientation. 2) If the normal attribute doesn't exist, but the velocity attribute does, then use the velocity attribute for orientation. 3) If neither the normal or the velocity attributes exist, then don't perform any orientation. One major difference is that the Copy SOP will automatically compute normals before step 3 is taken. This is not automatically done when instancing for rendering. |
Mon. February 17, 2003 | |
6.0.214 | When instancing geometry (or lights), orientation is now more consistent with the copy SOP. Rotating the orientation now works as follows: 1) If the normal attribute exists, use this to define the orientation. 2) If the normal attribute doesn't exist, but the velocity attribute does, then use the velocity attribute for orientation. 3) If neither the normal or the velocity attributes exist, then don't perform any orientation. One major difference is that the Copy SOP will automatically compute normals before step 3 is taken. This is not automatically done when instancing for rendering. |
Mon. February 17, 2003 |