Houdini Main Changelogs

6.2.16

Added "Set Current Values to Defaults" menu entry to Presets menu. It behaves as the corresponding entry in the parm menu, but does so for the entire set of parameters.

Thu. October 16, 2003
6.2.16

Added "Set Current Values to Defaults" menu entry to Presets menu. It behaves as the corresponding entry in the parm menu, but does so for the entire set of parameters.

Thu. October 16, 2003
6.2.16

Added "Set Current Values to Defaults" menu entry to Presets menu. It behaves as the corresponding entry in the parm menu, but does so for the entire set of parameters.

Thu. October 16, 2003
6.2.15

Fixed a couple of problems with the copinput VOP.

  • adding the component input caused the other inputs to shift,and existing VOPnets have all their inputs connected by index,which caused X,Y and Frame to be connected incorrectly, thusbreaking backwards compatibility with VOPs.
  • A strcmp in the #if signature line was formed incorrectly, andbroke the signatures for several types (resulting in monochrome (redchannel) output only).
Wed. October 15, 2003
6.2.15

Fixed a couple of problems with the copinput VOP.

  • adding the component input caused the other inputs to shift,and existing VOPnets have all their inputs connected by index,which caused X,Y and Frame to be connected incorrectly, thusbreaking backwards compatibility with VOPs.
  • A strcmp in the #if signature line was formed incorrectly, andbroke the signatures for several types (resulting in monochrome (redchannel) output only).
Wed. October 15, 2003
6.2.15

Fixed a couple of problems with the copinput VOP.

  • adding the component input caused the other inputs to shift,and existing VOPnets have all their inputs connected by index,which caused X,Y and Frame to be connected incorrectly, thusbreaking backwards compatibility with VOPs.
  • A strcmp in the #if signature line was formed incorrectly, andbroke the signatures for several types (resulting in monochrome (redchannel) output only).
Wed. October 15, 2003
6.2.15

Fixed a couple of problems with the copinput VOP.

  • adding the component input caused the other inputs to shift,and existing VOPnets have all their inputs connected by index,which caused X,Y and Frame to be connected incorrectly, thusbreaking backwards compatibility with VOPs.
  • A strcmp in the #if signature line was formed incorrectly, andbroke the signatures for several types (resulting in monochrome (redchannel) output only).
Wed. October 15, 2003
6.2.15

Fixed a couple of problems with the copinput VOP.

  • adding the component input caused the other inputs to shift,and existing VOPnets have all their inputs connected by index,which caused X,Y and Frame to be connected incorrectly, thusbreaking backwards compatibility with VOPs.
  • A strcmp in the #if signature line was formed incorrectly, andbroke the signatures for several types (resulting in monochrome (redchannel) output only).
Wed. October 15, 2003
6.2.15

A problem with ray-nonplanar quad intersection has been fixed. The Ray SOP should be more stable with quad meshes. The Brush tools should be less likely to paint through the geometry when painting on quadrilateral meshes. And the Inflate SOP should be less likely to miss points when working with quadrilateral meshes. These problems showed up at the edges of non-planar quads.

Wed. October 15, 2003
6.2.15

A problem with ray-nonplanar quad intersection has been fixed. The Ray SOP should be more stable with quad meshes. The Brush tools should be less likely to paint through the geometry when painting on quadrilateral meshes. And the Inflate SOP should be less likely to miss points when working with quadrilateral meshes. These problems showed up at the edges of non-planar quads.

Wed. October 15, 2003
6.2.15

A problem with ray-nonplanar quad intersection has been fixed. The Ray SOP should be more stable with quad meshes. The Brush tools should be less likely to paint through the geometry when painting on quadrilateral meshes. And the Inflate SOP should be less likely to miss points when working with quadrilateral meshes. These problems showed up at the edges of non-planar quads.

Wed. October 15, 2003
6.2.15

A problem with ray-nonplanar quad intersection has been fixed. The Ray SOP should be more stable with quad meshes. The Brush tools should be less likely to paint through the geometry when painting on quadrilateral meshes. And the Inflate SOP should be less likely to miss points when working with quadrilateral meshes. These problems showed up at the edges of non-planar quads.

Wed. October 15, 2003
6.2.15

A problem with ray-nonplanar quad intersection has been fixed. The Ray SOP should be more stable with quad meshes. The Brush tools should be less likely to paint through the geometry when painting on quadrilateral meshes. And the Inflate SOP should be less likely to miss points when working with quadrilateral meshes. These problems showed up at the edges of non-planar quads.

Wed. October 15, 2003
6.2.14

Houdini now properly coredumps when HOUDINI_COREDUMP is set but HOUDINI_UI_COREDUMP is not on Unix systems. This enables stack trace generation while still attempting to save the .hip file.

Tue. October 14, 2003
6.2.14

Houdini now properly coredumps when HOUDINI_COREDUMP is set but HOUDINI_UI_COREDUMP is not on Unix systems. This enables stack trace generation while still attempting to save the .hip file.

Tue. October 14, 2003
6.2.14

Houdini now properly coredumps when HOUDINI_COREDUMP is set but HOUDINI_UI_COREDUMP is not on Unix systems. This enables stack trace generation while still attempting to save the .hip file.

Tue. October 14, 2003
6.2.14

Houdini now properly coredumps when HOUDINI_COREDUMP is set but HOUDINI_UI_COREDUMP is not on Unix systems. This enables stack trace generation while still attempting to save the .hip file.

Tue. October 14, 2003
6.2.14

Houdini now properly coredumps when HOUDINI_COREDUMP is set but HOUDINI_UI_COREDUMP is not on Unix systems. This enables stack trace generation while still attempting to save the .hip file.

Tue. October 14, 2003
6.2.14

The Sticky Objects now have a rotation parameter to define their local 2d rotation about the surface normal. Sticky objects now also will treat any parent object that is a sticky as a 2d parenting hierarchy. This makes it possible to have stickies be driven by other stickies.

Tue. October 14, 2003
6.2.14

The Sticky Objects now have a rotation parameter to define their local 2d rotation about the surface normal. Sticky objects now also will treat any parent object that is a sticky as a 2d parenting hierarchy. This makes it possible to have stickies be driven by other stickies.

Tue. October 14, 2003
6.2.14

The Sticky Objects now have a rotation parameter to define their local 2d rotation about the surface normal. Sticky objects now also will treat any parent object that is a sticky as a 2d parenting hierarchy. This makes it possible to have stickies be driven by other stickies.

Tue. October 14, 2003
6.2.14

The Sticky Objects now have a rotation parameter to define their local 2d rotation about the surface normal. Sticky objects now also will treat any parent object that is a sticky as a 2d parenting hierarchy. This makes it possible to have stickies be driven by other stickies.

Tue. October 14, 2003
6.2.14

The Sticky Objects now have a rotation parameter to define their local 2d rotation about the surface normal. Sticky objects now also will treat any parent object that is a sticky as a 2d parenting hierarchy. This makes it possible to have stickies be driven by other stickies.

Tue. October 14, 2003
6.2.10

Added the Jiggle CHOP, which is similar to the Spring & Lag CHOPs, but works on vectors and uses a slightly different interface.

Fri. October 10, 2003
6.2.10

Added the Jiggle CHOP, which is similar to the Spring & Lag CHOPs, but works on vectors and uses a slightly different interface.

Fri. October 10, 2003