Houdini Main Changelogs

6.2.114

Left mouse button and middle mouse button clicks and drags on handles, including ladder handles, now highlights the parameter border to a bright yellow. When the left and middle mouse buttons are not pressed, the highlight is turned off. One can then quickly view handle bindings by using the middle mouse button without altering the parameter values as long as the cursor stays within the centre ladder box. More care is required when using the left mouse button to view handle bindings without changing parameter values.

Thu. January 22, 2004
6.2.114

Left mouse button and middle mouse button clicks and drags on handles, including ladder handles, now highlights the parameter border to a bright yellow. When the left and middle mouse buttons are not pressed, the highlight is turned off. One can then quickly view handle bindings by using the middle mouse button without altering the parameter values as long as the cursor stays within the centre ladder box. More care is required when using the left mouse button to view handle bindings without changing parameter values.

Thu. January 22, 2004
6.2.114

Left mouse button and middle mouse button clicks and drags on handles, including ladder handles, now highlights the parameter border to a bright yellow. When the left and middle mouse buttons are not pressed, the highlight is turned off. One can then quickly view handle bindings by using the middle mouse button without altering the parameter values as long as the cursor stays within the centre ladder box. More care is required when using the left mouse button to view handle bindings without changing parameter values.

Thu. January 22, 2004
6.2.114

Left mouse button and middle mouse button clicks and drags on handles, including ladder handles, now highlights the parameter border to a bright yellow. When the left and middle mouse buttons are not pressed, the highlight is turned off. One can then quickly view handle bindings by using the middle mouse button without altering the parameter values as long as the cursor stays within the centre ladder box. More care is required when using the left mouse button to view handle bindings without changing parameter values.

Thu. January 22, 2004
6.2.113

Initial work on a new collision algorithm to better detect collisions against potentially deforming geometry. The "Geometry Moves with Time" parameter has been made obsolete, and replaced with a new "Hint" menu which included the previous two behaviors along with the new one. The old parameter value is detected and automatically translated. Also fixed some bugs in collisions against static geometry which may have led to incorrectly rejecting some collisions.

Wed. January 21, 2004
6.2.113

Initial work on a new collision algorithm to better detect collisions against potentially deforming geometry. The "Geometry Moves with Time" parameter has been made obsolete, and replaced with a new "Hint" menu which included the previous two behaviors along with the new one. The old parameter value is detected and automatically translated. Also fixed some bugs in collisions against static geometry which may have led to incorrectly rejecting some collisions.

Wed. January 21, 2004
6.2.113

Initial work on a new collision algorithm to better detect collisions against potentially deforming geometry. The "Geometry Moves with Time" parameter has been made obsolete, and replaced with a new "Hint" menu which included the previous two behaviors along with the new one. The old parameter value is detected and automatically translated. Also fixed some bugs in collisions against static geometry which may have led to incorrectly rejecting some collisions.

Wed. January 21, 2004
6.2.113

Initial work on a new collision algorithm to better detect collisions against potentially deforming geometry. The "Geometry Moves with Time" parameter has been made obsolete, and replaced with a new "Hint" menu which included the previous two behaviors along with the new one. The old parameter value is detected and automatically translated. Also fixed some bugs in collisions against static geometry which may have led to incorrectly rejecting some collisions.

Wed. January 21, 2004
6.2.113

Initial work on a new collision algorithm to better detect collisions against potentially deforming geometry. The "Geometry Moves with Time" parameter has been made obsolete, and replaced with a new "Hint" menu which included the previous two behaviors along with the new one. The old parameter value is detected and automatically translated. Also fixed some bugs in collisions against static geometry which may have led to incorrectly rejecting some collisions.

Wed. January 21, 2004
6.2.113

Initial work on a new collision algorithm to better detect collisions against potentially deforming geometry. The "Geometry Moves with Time" parameter has been made obsolete, and replaced with a new "Hint" menu which included the previous two behaviors along with the new one. It currently only supports triangles, and does not support the "Oversampling" parameter, though it does support the "Bounce Accuracy" parameter, unlike the older method for moving geometry. Also fixed some bugs in collisions against static geometry which may have led to incorrectly rejecting some collisions.

Wed. January 21, 2004
6.2.113

Initial work on a new collision algorithm to better detect collisions against potentially deforming geometry. The "Geometry Moves with Time" parameter has been made obsolete, and replaced with a new "Hint" menu which included the previous two behaviors along with the new one. It currently only supports triangles, and does not support the "Oversampling" parameter, though it does support the "Bounce Accuracy" parameter, unlike the older method for moving geometry. Also fixed some bugs in collisions against static geometry which may have led to incorrectly rejecting some collisions.

Wed. January 21, 2004
6.2.113

Initial work on a new collision algorithm to better detect collisions against potentially deforming geometry. The "Geometry Moves with Time" parameter has been made obsolete, and replaced with a new "Hint" menu which included the previous two behaviors along with the new one. It currently only supports triangles, and does not support the "Oversampling" parameter, though it does support the "Bounce Accuracy" parameter, unlike the older method for moving geometry. Also fixed some bugs in collisions against static geometry which may have led to incorrectly rejecting some collisions.

Wed. January 21, 2004
6.2.113

Initial work on a new collision algorithm to better detect collisions against potentially deforming geometry. The "Geometry Moves with Time" parameter has been made obsolete, and replaced with a new "Hint" menu which included the previous two behaviors along with the new one. It currently only supports triangles, and does not support the "Oversampling" parameter, though it does support the "Bounce Accuracy" parameter, unlike the older method for moving geometry. Also fixed some bugs in collisions against static geometry which may have led to incorrectly rejecting some collisions.

Wed. January 21, 2004
6.2.113

Initial work on a new collision algorithm to better detect collisions against potentially deforming geometry. The "Geometry Moves with Time" parameter has been made obsolete, and replaced with a new "Hint" menu which included the previous two behaviors along with the new one. It currently only supports triangles, and does not support the "Oversampling" parameter, though it does support the "Bounce Accuracy" parameter, unlike the older method for moving geometry. Also fixed some bugs in collisions against static geometry which may have led to incorrectly rejecting some collisions.

Wed. January 21, 2004
6.2.113

Added the Border COP, which adds a colored border to the image by either increasing the resolution, or overwriting edge pixels. Each edge has its own border width, so this can be used to change resolutions without stretching the image (like converting a 16:9 format to 4:3 by adding bars).

Wed. January 21, 2004
6.2.113

Added the Border COP, which adds a colored border to the image by either increasing the resolution, or overwriting edge pixels. Each edge has its own border width, so this can be used to change resolutions without stretching the image (like converting a 16:9 format to 4:3 by adding bars).

Wed. January 21, 2004
6.2.113

Added the Border COP, which adds a colored border to the image by either increasing the resolution, or overwriting edge pixels. Each edge has its own border width, so this can be used to change resolutions without stretching the image (like converting a 16:9 format to 4:3 by adding bars).

Wed. January 21, 2004
6.2.113

Added the Border COP, which adds a colored border to the image by either increasing the resolution, or overwriting edge pixels. Each edge has its own border width, so this can be used to change resolutions without stretching the image (like converting a 16:9 format to 4:3 by adding bars).

Wed. January 21, 2004
6.2.113

Added the Border COP, which adds a colored border to the image by either increasing the resolution, or overwriting edge pixels. Each edge has its own border width, so this can be used to change resolutions without stretching the image (like converting a 16:9 format to 4:3 by adding bars).

Wed. January 21, 2004
6.2.112

Fixed a crash in the Layer/Composite COPs that would occur if the background sequence was outside its frame range, and a compositing operation that required background alpha was used (like Outside or Atop).

Tue. January 20, 2004
6.2.112

Fixed a crash in the Layer/Composite COPs that would occur if the background sequence was outside its frame range, and a compositing operation that required background alpha was used (like Outside or Atop).

Tue. January 20, 2004
6.2.112

Fixed a crash in the Layer/Composite COPs that would occur if the background sequence was outside its frame range, and a compositing operation that required background alpha was used (like Outside or Atop).

Tue. January 20, 2004
6.2.112

Fixed a crash in the Layer/Composite COPs that would occur if the background sequence was outside its frame range, and a compositing operation that required background alpha was used (like Outside or Atop).

Tue. January 20, 2004
6.2.112

Fixed a crash in the Layer/Composite COPs that would occur if the background sequence was outside its frame range, and a compositing operation that required background alpha was used (like Outside or Atop).

Tue. January 20, 2004
6.2.112

Fixed a variety of mplay problems:

  • Images received from other sources using -k or -K (render orflipbook) no longer crash if the 'Use Luminance Images for Single

Planes' is off, and the Alpha plane is selected.

  • Passing a .pic file to mplay using 'cat foo.pic | mplay stdin'

no longer swaps the channels incorrectly.

  • The frame range and Single Image options in the File->Open... dialog

for image sequences are now respected.

  • If -C is specified on the command line (precache images), imagesloaded via File->Open... will be precached.
Tue. January 20, 2004