Houdini Main Changelogs
 |
5.1.45 | We now have a Snap Operation which allows you to snap points together, either based on a tolerance or to a grid, without consolidating the point positions. |
Thu. March 7, 2002 |
|
5.1.45 | We now have a Snap Operation which allows you to snap points together, either based on a tolerance or to a grid, without consolidating the point positions. |
Thu. March 7, 2002 |
|
5.1.45 | We now have a Snap Operation which allows you to snap points together, either based on a tolerance or to a grid, without consolidating the point positions. |
Thu. March 7, 2002 |
|
5.1.45 | We now have a Snap Operation which allows you to snap points together, either based on a tolerance or to a grid, without consolidating the point positions. |
Thu. March 7, 2002 |
|
5.1.45 | We now have a Snap Operation which allows you to snap points together, either based on a tolerance or to a grid, without consolidating the point positions. |
Thu. March 7, 2002 |
|
5.1.45 | We no longer stash obsolete or detected corrupt view commands, and thus we don't resave them when the hip file is saved again. In addition, File > New now clears all the currently stashed commands, so the next save will only save view commands for the existing viewers. This should help alleviate some of the file bloat problems caused by viewdisplay commands. |
Thu. March 7, 2002 |
|
5.1.45 | We no longer stash obsolete or detected corrupt view commands, and thus we don't resave them when the hip file is saved again. In addition, File > New now clears all the currently stashed commands, so the next save will only save view commands for the existing viewers. This should help alleviate some of the file bloat problems caused by viewdisplay commands. |
Thu. March 7, 2002 |
|
5.1.45 | We no longer stash obsolete or detected corrupt view commands, and thus we don't resave them when the hip file is saved again. In addition, File > New now clears all the currently stashed commands, so the next save will only save view commands for the existing viewers. This should help alleviate some of the file bloat problems caused by viewdisplay commands. |
Thu. March 7, 2002 |
|
5.1.45 | We no longer stash obsolete or detected corrupt view commands, and thus we don't resave them when the hip file is saved again. In addition, File > New now clears all the currently stashed commands, so the next save will only save view commands for the existing viewers. This should help alleviate some of the file bloat problems caused by viewdisplay commands. |
Thu. March 7, 2002 |
|
5.1.45 | We no longer stash obsolete or detected corrupt view commands, and thus we don't resave them when the hip file is saved again. In addition, File > New now clears all the currently stashed commands, so the next save will only save view commands for the existing viewers. This should help alleviate some of the file bloat problems caused by viewdisplay commands. |
Thu. March 7, 2002 |
 |
5.1.44 | Fixed bug where renaming the second bone of a three bone IK chain would cause the bone chain to change position in the viewport. However, it restored itself as soon as the tile of the second bone was clicked on. |
Wed. March 6, 2002 |
|
5.1.44 | Fixed bug where renaming the second bone of a three bone IK chain would cause the bone chain to change position in the viewport. However, it restored itself as soon as the tile of the second bone was clicked on. |
Wed. March 6, 2002 |
|
5.1.44 | Fixed bug where renaming the second bone of a three bone IK chain would cause the bone chain to change position in the viewport. However, it restored itself as soon as the tile of the second bone was clicked on. |
Wed. March 6, 2002 |
|
5.1.44 | Fixed bug where renaming the second bone of a three bone IK chain would cause the bone chain to change position in the viewport. However, it restored itself as soon as the tile of the second bone was clicked on. |
Wed. March 6, 2002 |
|
5.1.44 | Fixed bug where renaming the second bone of a three bone IK chain would cause the bone chain to change position in the viewport. However, it restored itself as soon as the tile of the second bone was clicked on. |
Wed. March 6, 2002 |
|
5.1.44 | Extra inputs (eg. naming dependencies) between operators are no longer saved in hip files. If they exist in the hip file, then they are silently ignored. If requested, they can be saved by setting the environment variable HOUDINI_SAVE_EXTRAINPUTS so that versions prior to 5.1 can load the file with pregenerated operator dependencies. In versions prior to Houdini 5.1, extra inputs were saved and reloaded so that naming dependencies could be maintained without cooking. eg. Renaming an operator will also rename all channel references to it. This was because naming dependencies would only be generated when an operator cooked and loading a hip file does not necessarily cook the operators. This is especially true if loading a file in hscript. Starting with Houdini 5.1, naming dependencies are generated regardless of whether an operator is cooked and so saving extra inputs are not needed. Furthermore, when loading hip files, extra inputs are now silently ignored if they happen to exist. |
Wed. March 6, 2002 |
|
5.1.44 | Extra inputs (eg. naming dependencies) between operators are no longer saved in hip files. If they exist in the hip file, then they are silently ignored. If requested, they can be saved by setting the environment variable HOUDINI_SAVE_EXTRAINPUTS so that versions prior to 5.1 can load the file with pregenerated operator dependencies. In versions prior to Houdini 5.1, extra inputs were saved and reloaded so that naming dependencies could be maintained without cooking. eg. Renaming an operator will also rename all channel references to it. This was because naming dependencies would only be generated when an operator cooked and loading a hip file does not necessarily cook the operators. This is especially true if loading a file in hscript. Starting with Houdini 5.1, naming dependencies are generated regardless of whether an operator is cooked and so saving extra inputs are not needed. Furthermore, when loading hip files, extra inputs are now silently ignored if they happen to exist. |
Wed. March 6, 2002 |
|
5.1.44 | Extra inputs (eg. naming dependencies) between operators are no longer saved in hip files. If they exist in the hip file, then they are silently ignored. If requested, they can be saved by setting the environment variable HOUDINI_SAVE_EXTRAINPUTS so that versions prior to 5.1 can load the file with pregenerated operator dependencies. In versions prior to Houdini 5.1, extra inputs were saved and reloaded so that naming dependencies could be maintained without cooking. eg. Renaming an operator will also rename all channel references to it. This was because naming dependencies would only be generated when an operator cooked and loading a hip file does not necessarily cook the operators. This is especially true if loading a file in hscript. Starting with Houdini 5.1, naming dependencies are generated regardless of whether an operator is cooked and so saving extra inputs are not needed. Furthermore, when loading hip files, extra inputs are now silently ignored if they happen to exist. |
Wed. March 6, 2002 |
|
5.1.44 | Extra inputs (eg. naming dependencies) between operators are no longer saved in hip files. If they exist in the hip file, then they are silently ignored. If requested, they can be saved by setting the environment variable HOUDINI_SAVE_EXTRAINPUTS so that versions prior to 5.1 can load the file with pregenerated operator dependencies. In versions prior to Houdini 5.1, extra inputs were saved and reloaded so that naming dependencies could be maintained without cooking. eg. Renaming an operator will also rename all channel references to it. This was because naming dependencies would only be generated when an operator cooked and loading a hip file does not necessarily cook the operators. This is especially true if loading a file in hscript. Starting with Houdini 5.1, naming dependencies are generated regardless of whether an operator is cooked and so saving extra inputs are not needed. Furthermore, when loading hip files, extra inputs are now silently ignored if they happen to exist. |
Wed. March 6, 2002 |
|
5.1.44 | Extra inputs (eg. naming dependencies) between operators are no longer saved in hip files. If they exist in the hip file, then they are silently ignored. If requested, they can be saved by setting the environment variable HOUDINI_SAVE_EXTRAINPUTS so that versions prior to 5.1 can load the file with pregenerated operator dependencies. In versions prior to Houdini 5.1, extra inputs were saved and reloaded so that naming dependencies could be maintained without cooking. eg. Renaming an operator will also rename all channel references to it. This was because naming dependencies would only be generated when an operator cooked and loading a hip file does not necessarily cook the operators. This is especially true if loading a file in hscript. Starting with Houdini 5.1, naming dependencies are generated regardless of whether an operator is cooked and so saving extra inputs are not needed. Furthermore, when loading hip files, extra inputs are now silently ignored if they happen to exist. |
Wed. March 6, 2002 |
|
5.1.44 | Custom panels no longer load automatically from disk. They are now saved to and loaded from hip files. The values in the custom panel are still not properly saved or loaded though. |
Wed. March 6, 2002 |
|
5.1.44 | Custom panels no longer load automatically from disk. They are now saved to and loaded from hip files. The values in the custom panel are still not properly saved or loaded though. |
Wed. March 6, 2002 |
|
5.1.44 | Custom panels no longer load automatically from disk. They are now saved to and loaded from hip files. The values in the custom panel are still not properly saved or loaded though. |
Wed. March 6, 2002 |
|
5.1.44 | Custom panels no longer load automatically from disk. They are now saved to and loaded from hip files. The values in the custom panel are still not properly saved or loaded though. |
Wed. March 6, 2002 |
|
5.1.44 | Custom panels no longer load automatically from disk. They are now saved to and loaded from hip files. The values in the custom panel are still not properly saved or loaded though. |
Wed. March 6, 2002 |