Houdini Main Changelogs

8.0.357

Major speed improvements have been made to the CaptureProximity SOP for large typical cases.

Thu. September 8, 2005
8.0.357

Major speed improvements have been made to the CaptureProximity SOP for large typical cases.

Thu. September 8, 2005
8.0.357

Major speed improvements have been made to the CaptureProximity SOP for large typical cases.

Thu. September 8, 2005
8.0.357

A bug has been fixed in the CaptureProximity SOP where bones that are aligned to one of the SOP's axes would sometimes not be picked even if it was closer to the point than a competing bone. This might affect the weighting of existing hip files. To maintain the weighting from old hip files, please lock the SOPs first.

Thu. September 8, 2005
8.0.357

A bug has been fixed in the CaptureProximity SOP where bones that are aligned to one of the SOP's axes would sometimes not be picked even if it was closer to the point than a competing bone. This might affect the weighting of existing hip files. To maintain the weighting from old hip files, please lock the SOPs first.

Thu. September 8, 2005
8.0.357

A bug has been fixed in the CaptureProximity SOP where bones that are aligned to one of the SOP's axes would sometimes not be picked even if it was closer to the point than a competing bone. This might affect the weighting of existing hip files. To maintain the weighting from old hip files, please lock the SOPs first.

Thu. September 8, 2005
8.0.357

A bug has been fixed in the CaptureProximity SOP where bones that are aligned to one of the SOP's axes would sometimes not be picked even if it was closer to the point than a competing bone. This might affect the weighting of existing hip files. To maintain the weighting from old hip files, please lock the SOPs first.

Thu. September 8, 2005
8.0.357

A bug has been fixed in the CaptureProximity SOP where bones that are aligned to one of the SOP's axes would sometimes not be picked even if it was closer to the point than a competing bone. This might affect the weighting of existing hip files. To maintain the weighting from old hip files, please lock the SOPs first.

Thu. September 8, 2005
8.0.357

A bug has been fixed in the CaptureProximity SOP where bones that are aligned to one of the SOP's axes would sometimes not be picked even if it was closer to the point than a competing bone. This might affect the weighting of existing hip files. To maintain the weighting from old hip files, please lock the SOPs first.

Thu. September 8, 2005
8.0.357

A bug has been fixed in the CaptureProximity SOP where bones that are aligned to one of the SOP's axes would sometimes not be picked even if it was closer to the point than a competing bone. This might affect the weighting of existing hip files. To maintain the weighting from old hip files, please lock the SOPs first.

Thu. September 8, 2005
8.0.357

A bug has been fixed in the CaptureProximity SOP where bones that are aligned to one of the SOP's axes would sometimes not be picked even if it was closer to the point than a competing bone. This might affect the weighting of existing hip files. To maintain the weighting from old hip files, please lock the SOPs first.

Thu. September 8, 2005
8.0.357

A bug has been fixed in the CaptureProximity SOP where bones that are aligned to one of the SOP's axes would sometimes not be picked even if it was closer to the point than a competing bone. This might affect the weighting of existing hip files. To maintain the weighting from old hip files, please lock the SOPs first.

Thu. September 8, 2005
8.0.357

A bug has been fixed in the CaptureProximity SOP where bones that are aligned to one of the SOP's axes would sometimes not be picked even if it was closer to the point than a competing bone. This might affect the weighting of existing hip files. To maintain the weighting from old hip files, please lock the SOPs first.

Thu. September 8, 2005
8.0.357

Fixed a couple of bugs in the Fetch CHOP:

  • When fetching a parm overriden by another CHOP, fetch the CHOP datachannel.
  • If Fetch doesn't fetch any channels, set the sample rate to the globalframe rate, rather than leaving it floating.
Thu. September 8, 2005
8.0.357

Fixed a couple of bugs in the Fetch CHOP:

  • When fetching a parm overriden by another CHOP, fetch the CHOP datachannel.
  • If Fetch doesn't fetch any channels, set the sample rate to the globalframe rate, rather than leaving it floating.
Thu. September 8, 2005
8.0.357

Fixed a couple of bugs in the Fetch CHOP:

  • When fetching a parm overriden by another CHOP, fetch the CHOP datachannel.
  • If Fetch doesn't fetch any channels, set the sample rate to the globalframe rate, rather than leaving it floating.
Thu. September 8, 2005
8.0.357

Fixed a couple of bugs in the Fetch CHOP:

  • When fetching a parm overriden by another CHOP, fetch the CHOP datachannel.
  • If Fetch doesn't fetch any channels, set the sample rate to the globalframe rate, rather than leaving it floating.
Thu. September 8, 2005
8.0.357

Fixed a couple of bugs in the Fetch CHOP:

  • When fetching a parm overriden by another CHOP, fetch the CHOP datachannel.
  • If Fetch doesn't fetch any channels, set the sample rate to the globalframe rate, rather than leaving it floating.
Thu. September 8, 2005
8.0.357

Fixed a bug where sychronizing a digital asset could fail if the asset contained an attribute pop whose popnet was being viewed by a pop viewer.

Thu. September 8, 2005
8.0.357

Fixed a bug where sychronizing a digital asset could fail if the asset contained an attribute pop whose popnet was being viewed by a pop viewer.

Thu. September 8, 2005
8.0.357

Fixed a bug where sychronizing a digital asset could fail if the asset contained an attribute pop whose popnet was being viewed by a pop viewer.

Thu. September 8, 2005
8.0.357

Fixed a bug where sychronizing a digital asset could fail if the asset contained an attribute pop whose popnet was being viewed by a pop viewer.

Thu. September 8, 2005
8.0.357

Fixed a bug where sychronizing a digital asset could fail if the asset contained an attribute pop whose popnet was being viewed by a pop viewer.

Thu. September 8, 2005
8.0.357

The way in which RBD determines if it should use edges has changed at the low level. Previously, it would look at the existance of a "SphereEdgeTree", and if missing, a "SphereTree" subdata to the Geometry. Now it looks only for "SphereTree" and looks at the resulting type.

This does not affect systems built out of higher level DOP nodes as the higher level nodes have been updated to reflect this change.

Thu. September 8, 2005
8.0.357

The way in which RBD determines if it should use edges has changed at the low level. Previously, it would look at the existance of a "SphereEdgeTree", and if missing, a "SphereTree" subdata to the Geometry. Now it looks only for "SphereTree" and looks at the resulting type.

This does not affect systems built out of higher level DOP nodes as the higher level nodes have been updated to reflect this change.

Thu. September 8, 2005