Houdini Main Changelogs
7.2.152 | Added new expression function: matrix mobjlookat(string base_node, string target_node, vector up_vector) which does a Look At from the base_node to the target_node taking in consideration an up vector. |
Tue. February 15, 2005 | |
7.2.152 | Added new expression function: matrix mobjlookat(string base_node, string target_node, vector up_vector) which does a Look At from the base_node to the target_node taking in consideration an up vector. |
Tue. February 15, 2005 | |
7.2.152 | Added new expression function: matrix mobjlookat(string base_node, string target_node, vector up_vector) which does a Look At from the base_node to the target_node taking in consideration an up vector. |
Tue. February 15, 2005 | |
7.2.152 | Added new expression function: matrix mobjlookat(string base_node, string target_node, vector up_vector) which does a Look At from the base_node to the target_node taking in consideration an up vector. |
Tue. February 15, 2005 | |
7.2.152 | The transform and rotation order in objects are now evaluated with the current animation time. Previously, they only used a value of 0 since they were non-animatible parameters. However, if they had a !!ch()!! reference, then they could then cause other operators to cook at the undesirable time value of 0. |
Tue. February 15, 2005 | |
7.2.152 | The transform and rotation order in objects are now evaluated with the current animation time. Previously, they only used a value of 0 since they were non-animatible parameters. However, if they had a !!ch()!! reference, then they could then cause other operators to cook at the undesirable time value of 0. |
Tue. February 15, 2005 | |
7.2.152 | The transform and rotation order in objects are now evaluated with the current animation time. Previously, they only used a value of 0 since they were non-animatible parameters. However, if they had a !!ch()!! reference, then they could then cause other operators to cook at the undesirable time value of 0. |
Tue. February 15, 2005 | |
7.2.152 | The transform and rotation order in objects are now evaluated with the current animation time. Previously, they only used a value of 0 since they were non-animatible parameters. However, if they had a !!ch()!! reference, then they could then cause other operators to cook at the undesirable time value of 0. |
Tue. February 15, 2005 | |
7.2.152 | The transform and rotation order in objects are now evaluated with the current animation time. Previously, they only used a value of 0 since they were non-animatible parameters. However, if they had a !!ch()!! reference, then they could then cause other operators to cook at the undesirable time value of 0. |
Tue. February 15, 2005 | |
7.2.152 | Fixed a bug that could cause opchangetype command to crash. |
Tue. February 15, 2005 | |
7.2.152 | Fixed a bug that could cause opchangetype command to crash. |
Tue. February 15, 2005 | |
7.2.152 | Fixed a bug that could cause opchangetype command to crash. |
Tue. February 15, 2005 | |
7.2.152 | Fixed a bug that could cause opchangetype command to crash. |
Tue. February 15, 2005 | |
7.2.152 | Fixed a bug that could cause opchangetype command to crash. |
Tue. February 15, 2005 | |
7.2.152 | The bundle chooser will now resolve a correct path at the ROP level, and not have the assumption that node names are relative to "/obj". |
Tue. February 15, 2005 | |
7.2.152 | The bundle chooser will now resolve a correct path at the ROP level, and not have the assumption that node names are relative to "/obj". |
Tue. February 15, 2005 | |
7.2.152 | The bundle chooser will now resolve a correct path at the ROP level, and not have the assumption that node names are relative to "/obj". |
Tue. February 15, 2005 | |
7.2.152 | The bundle chooser will now resolve a correct path at the ROP level, and not have the assumption that node names are relative to "/obj". |
Tue. February 15, 2005 | |
7.2.152 | The bundle chooser will now resolve a correct path at the ROP level, and not have the assumption that node names are relative to "/obj". |
Tue. February 15, 2005 | |
7.2.151 | Fixed bug that could cause Houdini to crash in certain cases when trying to read an invalid image file (or one with an incorrect extension). |
Mon. February 14, 2005 | |
7.2.151 | Fixed bug that could cause Houdini to crash in certain cases when trying to read an invalid image file (or one with an incorrect extension). |
Mon. February 14, 2005 | |
7.2.151 | Fixed bug that could cause Houdini to crash in certain cases when trying to read an invalid image file (or one with an incorrect extension). |
Mon. February 14, 2005 | |
7.2.151 | Fixed bug that could cause Houdini to crash in certain cases when trying to read an invalid image file (or one with an incorrect extension). |
Mon. February 14, 2005 | |
7.2.151 | Fixed bug that could cause Houdini to crash in certain cases when trying to read an invalid image file (or one with an incorrect extension). |
Mon. February 14, 2005 | |
7.2.151 |
|
Mon. February 14, 2005 |