Houdini Main Changelogs
4.9.556 | Backward compatibility is a goal we always keep in mind from one major release to the next. Sometimes, however, a new and better technology cannot be embedded in the fabric of the software without dislocating an older technology, often causing an incompatibility with the previous release. The purpose of this file is to ease the user's transition to a new release by documenting the unexpected changes in the way existing functions work. Anything from a change of hotkey to a change in file format or default parameter value should be recorded here. parameter value should be recorded here. |
Fri. December 7, 2001 | |
4.9.556 | Backward compatibility is a goal we always keep in mind from one major release to the next. Sometimes, however, a new and better technology cannot be embedded in the fabric of the software without dislocating an older technology, often causing an incompatibility with the previous release. The purpose of this file is to ease the user's transition to a new release by documenting the unexpected changes in the way existing functions work. Anything from a change of hotkey to a change in file format or default parameter value should be recorded here. parameter value should be recorded here. |
Fri. December 7, 2001 | |
4.9.556 | Backward compatibility is a goal we always keep in mind from one major release to the next. Sometimes, however, a new and better technology cannot be embedded in the fabric of the software without dislocating an older technology, often causing an incompatibility with the previous release. The purpose of this file is to ease the user's transition to a new release by documenting the unexpected changes in the way existing functions work. Anything from a change of hotkey to a change in file format or default parameter value should be recorded here. parameter value should be recorded here. |
Fri. December 7, 2001 | |
4.9.556 | Backward compatibility is a goal we always keep in mind from one major release to the next. Sometimes, however, a new and better technology cannot be embedded in the fabric of the software without dislocating an older technology, often causing an incompatibility with the previous release. The purpose of this file is to ease the user's transition to a new release by documenting the unexpected changes in the way existing functions work. Anything from a change of hotkey to a change in file format or default parameter value should be recorded here. parameter value should be recorded here. |
Fri. December 7, 2001 | |
4.9.556 | The Sphere, Circle, Tube, and Torus all now have a consistent orientation. When the axis to orient to is up in the viewport, the front side should have the vertices going from left to right. Most of the primitives and axis combinations already did this, so there will be no change. However some (notably the Tube) will have different point orders than before. To recover the old behaviour, append a transform SOP and rotate by 180 degrees about the secondary axis. |
Fri. December 7, 2001 | |
4.9.556 | The Sphere, Circle, Tube, and Torus all now have a consistent orientation. When the axis to orient to is up in the viewport, the front side should have the vertices going from left to right. Most of the primitives and axis combinations already did this, so there will be no change. However some (notably the Tube) will have different point orders than before. To recover the old behaviour, append a transform SOP and rotate by 180 degrees about the secondary axis. |
Fri. December 7, 2001 | |
4.9.556 | The Sphere, Circle, Tube, and Torus all now have a consistent orientation. When the axis to orient to is up in the viewport, the front side should have the vertices going from left to right. Most of the primitives and axis combinations already did this, so there will be no change. However some (notably the Tube) will have different point orders than before. To recover the old behaviour, append a transform SOP and rotate by 180 degrees about the secondary axis. |
Fri. December 7, 2001 | |
4.9.556 | The Sphere, Circle, Tube, and Torus all now have a consistent orientation. When the axis to orient to is up in the viewport, the front side should have the vertices going from left to right. Most of the primitives and axis combinations already did this, so there will be no change. However some (notably the Tube) will have different point orders than before. To recover the old behaviour, append a transform SOP and rotate by 180 degrees about the secondary axis. |
Fri. December 7, 2001 | |
4.9.556 | The Sphere, Circle, Tube, and Torus all now have a consistent orientation. When the axis to orient to is up in the viewport, the front side should have the vertices going from left to right. Most of the primitives and axis combinations already did this, so there will be no change. However some (notably the Tube) will have different point orders than before. To recover the old behaviour, append a transform SOP and rotate by 180 degrees about the secondary axis. |
Fri. December 7, 2001 | |
4.9.555 |
|
Thu. December 6, 2001 | |
4.9.555 |
|
Thu. December 6, 2001 | |
4.9.555 |
|
Thu. December 6, 2001 | |
4.9.555 |
|
Thu. December 6, 2001 | |
4.9.555 |
|
Thu. December 6, 2001 | |
4.9.555 | The Sweep, Revolve, and Skin Surface Operations now default to converting meshes to polygons. For backwards compatibility, these flags should be turned off. |
Thu. December 6, 2001 | |
4.9.555 | The Sweep, Revolve, and Skin Surface Operations now default to converting meshes to polygons. For backwards compatibility, these flags should be turned off. |
Thu. December 6, 2001 | |
4.9.555 | The Sweep, Revolve, and Skin Surface Operations now default to converting meshes to polygons. For backwards compatibility, these flags should be turned off. |
Thu. December 6, 2001 | |
4.9.555 | The Sweep, Revolve, and Skin Surface Operations now default to converting meshes to polygons. For backwards compatibility, these flags should be turned off. |
Thu. December 6, 2001 | |
4.9.555 | The Sweep, Revolve, and Skin Surface Operations now default to converting meshes to polygons. For backwards compatibility, these flags should be turned off. |
Thu. December 6, 2001 | |
4.9.554 | Object level operations for generating objects now highlight the object being operated on. The Multi-Object operation has an option to highlight selected objects if desired. In both cases, the highlighting works even if the display flag for the object is off, so it is much easier to manipulate objects with their display flag off. |
Wed. December 5, 2001 | |
4.9.554 | Object level operations for generating objects now highlight the object being operated on. The Multi-Object operation has an option to highlight selected objects if desired. In both cases, the highlighting works even if the display flag for the object is off, so it is much easier to manipulate objects with their display flag off. |
Wed. December 5, 2001 | |
4.9.554 | Object level operations for generating objects now highlight the object being operated on. The Multi-Object operation has an option to highlight selected objects if desired. In both cases, the highlighting works even if the display flag for the object is off, so it is much easier to manipulate objects with their display flag off. |
Wed. December 5, 2001 | |
4.9.554 | Object level operations for generating objects now highlight the object being operated on. The Multi-Object operation has an option to highlight selected objects if desired. In both cases, the highlighting works even if the display flag for the object is off, so it is much easier to manipulate objects with their display flag off. |
Wed. December 5, 2001 | |
4.9.554 | Object level operations for generating objects now highlight the object being operated on. The Multi-Object operation has an option to highlight selected objects if desired. In both cases, the highlighting works even if the display flag for the object is off, so it is much easier to manipulate objects with their display flag off. |
Wed. December 5, 2001 | |
4.9.553 | Bug was fixed where the "Remove Kinematics" option in the Bones operation on IK w/Twist affector bone chains could cause Houdini to crash (not necessarily right away). |
Tue. December 4, 2001 |