Main

Houdini Main Changelogs

4.9.589

The oplocate command returns absolute coordinates on the worksheet that are unchanged by panning or zooming the worksheet. Previously, they were dependent upon the view currently open on the worksheet.

 Thu. January 10, 2002
4.9.589

The oplocate command returns absolute coordinates on the worksheet that are unchanged by panning or zooming the worksheet. Previously, they were dependent upon the view currently open on the worksheet.

 Thu. January 10, 2002
4.9.589

The oplocate command returns absolute coordinates on the worksheet that are unchanged by panning or zooming the worksheet. Previously, they were dependent upon the view currently open on the worksheet.

 Thu. January 10, 2002
4.9.589

The oplocate command returns absolute coordinates on the worksheet that are unchanged by panning or zooming the worksheet. Previously, they were dependent upon the view currently open on the worksheet.

 Thu. January 10, 2002
4.9.589

Templated sops can now draw point normals, point texture coordinates, and vertex texture coordinates.

 Thu. January 10, 2002
4.9.589

Templated sops can now draw point normals, point texture coordinates, and vertex texture coordinates.

 Thu. January 10, 2002
4.9.589

Templated sops can now draw point normals, point texture coordinates, and vertex texture coordinates.

 Thu. January 10, 2002
4.9.589

Templated sops can now draw point normals, point texture coordinates, and vertex texture coordinates.

 Thu. January 10, 2002
4.9.589

Templated sops can now draw point normals, point texture coordinates, and vertex texture coordinates.

 Thu. January 10, 2002
4.9.589

When no group is specified in Peak, it will now peak all points rather than all primitives as before.

 Thu. January 10, 2002
4.9.589

When no group is specified in Peak, it will now peak all points rather than all primitives as before.

 Thu. January 10, 2002
4.9.589

When no group is specified in Peak, it will now peak all points rather than all primitives as before.

 Thu. January 10, 2002
4.9.589

When no group is specified in Peak, it will now peak all points rather than all primitives as before.

 Thu. January 10, 2002
4.9.589

When no group is specified in Peak, it will now peak all points rather than all primitives as before.

 Thu. January 10, 2002
4.9.589

The LSystem SOP with point attribute generation turned on behaves differently. First, there are several new attributes created. This can be worked around by appending an attribute SOP to delete the unwanted attributes. Second, the points are reordered to ensure frame to frame coherence. There is no work around to this behaviour, except in some cases a Sort by Vertex Order may work.

 Thu. January 10, 2002
4.9.589

The LSystem SOP with point attribute generation turned on behaves differently. First, there are several new attributes created. This can be worked around by appending an attribute SOP to delete the unwanted attributes. Second, the points are reordered to ensure frame to frame coherence. There is no work around to this behaviour, except in some cases a Sort by Vertex Order may work.

 Thu. January 10, 2002
4.9.589

The LSystem SOP with point attribute generation turned on behaves differently. First, there are several new attributes created. This can be worked around by appending an attribute SOP to delete the unwanted attributes. Second, the points are reordered to ensure frame to frame coherence. There is no work around to this behaviour, except in some cases a Sort by Vertex Order may work.

 Thu. January 10, 2002
4.9.589

The LSystem SOP with point attribute generation turned on behaves differently. First, there are several new attributes created. This can be worked around by appending an attribute SOP to delete the unwanted attributes. Second, the points are reordered to ensure frame to frame coherence. There is no work around to this behaviour, except in some cases a Sort by Vertex Order may work.

 Thu. January 10, 2002
4.9.589

The LSystem SOP with point attribute generation turned on behaves differently. First, there are several new attributes created. This can be worked around by appending an attribute SOP to delete the unwanted attributes. Second, the points are reordered to ensure frame to frame coherence. There is no work around to this behaviour, except in some cases a Sort by Vertex Order may work.

 Thu. January 10, 2002
4.9.589

This change was made in 4.9.446 but not documented. In the LSystem SOP, various improvements were made:

  • The point width attribute is multiplied by the thickness valueof the lsystem, so will match the diameters of the tubegeneration.
  • Generations over 127 produce the correct generation number.
  • When point attributes are generated, we create more than justthe width attribute:
  • segs ($SEGS), an integer point attribute for the number of

segments (rows) tubes leaving that point should have.

  • div ($DIV), an integer point attribute for the number ofdivisions (columns) tubes leaving that point should have.
  • lage ($LAGE), the age of the point in the lsystem.
  • arc ($ARC), the arc length from that point to the root ofthe lsystem.
  • up ($UP[XYZ), the up vector for the tubes birthed at thatpoint.
  • gen ($GEN), the integer generation of that point.
    • When point attributes are created, the system's points areautomatically sorted by generation. This means point numberswill match from generation to generation, allowing motion blur,etc.
 Thu. January 10, 2002
4.9.589

This change was made in 4.9.446 but not documented. In the LSystem SOP, various improvements were made:

  • The point width attribute is multiplied by the thickness valueof the lsystem, so will match the diameters of the tubegeneration.
  • Generations over 127 produce the correct generation number.
  • When point attributes are generated, we create more than justthe width attribute:
  • segs ($SEGS), an integer point attribute for the number of

segments (rows) tubes leaving that point should have.

  • div ($DIV), an integer point attribute for the number ofdivisions (columns) tubes leaving that point should have.
  • lage ($LAGE), the age of the point in the lsystem.
  • arc ($ARC), the arc length from that point to the root ofthe lsystem.
  • up ($UP[XYZ), the up vector for the tubes birthed at thatpoint.
  • gen ($GEN), the integer generation of that point.
    • When point attributes are created, the system's points areautomatically sorted by generation. This means point numberswill match from generation to generation, allowing motion blur,etc.
 Thu. January 10, 2002
4.9.589

This change was made in 4.9.446 but not documented. In the LSystem SOP, various improvements were made:

  • The point width attribute is multiplied by the thickness valueof the lsystem, so will match the diameters of the tubegeneration.
  • Generations over 127 produce the correct generation number.
  • When point attributes are generated, we create more than justthe width attribute:
  • segs ($SEGS), an integer point attribute for the number of

segments (rows) tubes leaving that point should have.

  • div ($DIV), an integer point attribute for the number ofdivisions (columns) tubes leaving that point should have.
  • lage ($LAGE), the age of the point in the lsystem.
  • arc ($ARC), the arc length from that point to the root ofthe lsystem.
  • up ($UP[XYZ), the up vector for the tubes birthed at thatpoint.
  • gen ($GEN), the integer generation of that point.
    • When point attributes are created, the system's points areautomatically sorted by generation. This means point numberswill match from generation to generation, allowing motion blur,etc.
 Thu. January 10, 2002
4.9.589

This change was made in 4.9.446 but not documented. In the LSystem SOP, various improvements were made:

  • The point width attribute is multiplied by the thickness valueof the lsystem, so will match the diameters of the tubegeneration.
  • Generations over 127 produce the correct generation number.
  • When point attributes are generated, we create more than justthe width attribute:
  • segs ($SEGS), an integer point attribute for the number of

segments (rows) tubes leaving that point should have.

  • div ($DIV), an integer point attribute for the number ofdivisions (columns) tubes leaving that point should have.
  • lage ($LAGE), the age of the point in the lsystem.
  • arc ($ARC), the arc length from that point to the root ofthe lsystem.
  • up ($UP[XYZ), the up vector for the tubes birthed at thatpoint.
  • gen ($GEN), the integer generation of that point.
    • When point attributes are created, the system's points areautomatically sorted by generation. This means point numberswill match from generation to generation, allowing motion blur,etc.
 Thu. January 10, 2002
4.9.589

This change was made in 4.9.446 but not documented. In the LSystem SOP, various improvements were made:

  • The point width attribute is multiplied by the thickness valueof the lsystem, so will match the diameters of the tubegeneration.
  • Generations over 127 produce the correct generation number.
  • When point attributes are generated, we create more than justthe width attribute:
  • segs ($SEGS), an integer point attribute for the number of

segments (rows) tubes leaving that point should have.

  • div ($DIV), an integer point attribute for the number ofdivisions (columns) tubes leaving that point should have.
  • lage ($LAGE), the age of the point in the lsystem.
  • arc ($ARC), the arc length from that point to the root ofthe lsystem.
  • up ($UP[XYZ), the up vector for the tubes birthed at thatpoint.
  • gen ($GEN), the integer generation of that point.
    • When point attributes are created, the system's points areautomatically sorted by generation. This means point numberswill match from generation to generation, allowing motion blur,etc.
 Thu. January 10, 2002
4.9.588

The HOUDINI_OUTLINEFONT_PATH now includes $WINDIR\Fonts.

 Wed. January 9, 2002
Houdini 20.5 | Houdini 20.0 | Houdini 19.5 | Houdini 19.0 | Houdini 18.5