Houdini Main Changelogs
9.0.339 | The PolySplit State will now output more than two decimal points for split ratios. This means that the split location will not change after hitting RMB and should ensure perpindicular splits stay that way. |
Tue. August 29, 2006 | |
9.0.339 | The PolySplit State will now output more than two decimal points for split ratios. This means that the split location will not change after hitting RMB and should ensure perpindicular splits stay that way. |
Tue. August 29, 2006 | |
9.0.339 | The PolySplit State will now output more than two decimal points for split ratios. This means that the split location will not change after hitting RMB and should ensure perpindicular splits stay that way. |
Tue. August 29, 2006 | |
9.0.339 | The PolySplit State will now output more than two decimal points for split ratios. This means that the split location will not change after hitting RMB and should ensure perpindicular splits stay that way. |
Tue. August 29, 2006 | |
9.0.339 | The LSystem SOP now properly treats expressions like F[fF] to be the same as FfF, allowing branches to fully break from the main trunk. |
Tue. August 29, 2006 | |
9.0.339 | The LSystem SOP now properly treats expressions like F[fF] to be the same as FfF, allowing branches to fully break from the main trunk. |
Tue. August 29, 2006 | |
9.0.339 | The LSystem SOP now properly treats expressions like F[fF] to be the same as FfF, allowing branches to fully break from the main trunk. |
Tue. August 29, 2006 | |
9.0.339 | The LSystem SOP now properly treats expressions like F[fF] to be the same as FfF, allowing branches to fully break from the main trunk. |
Tue. August 29, 2006 | |
9.0.339 | The LSystem SOP now properly treats expressions like F[fF] to be the same as FfF, allowing branches to fully break from the main trunk. |
Tue. August 29, 2006 | |
9.0.339 | The LSystem SOP will now produce different output for F[fF] than before. It will now be the same as FfF as expected. The use of f or h commands will no longer automatically join to the root of the previous tree, but create disjoint geometry as expected. |
Tue. August 29, 2006 | |
9.0.339 | The LSystem SOP will now produce different output for F[fF] than before. It will now be the same as FfF as expected. The use of f or h commands will no longer automatically join to the root of the previous tree, but create disjoint geometry as expected. |
Tue. August 29, 2006 | |
9.0.339 | The LSystem SOP will now produce different output for F[fF] than before. It will now be the same as FfF as expected. The use of f or h commands will no longer automatically join to the root of the previous tree, but create disjoint geometry as expected. |
Tue. August 29, 2006 | |
9.0.339 | The LSystem SOP will now produce different output for F[fF] than before. It will now be the same as FfF as expected. The use of f or h commands will no longer automatically join to the root of the previous tree, but create disjoint geometry as expected. |
Tue. August 29, 2006 | |
9.0.339 | The LSystem SOP will now produce different output for F[fF] than before. It will now be the same as FfF as expected. The use of f or h commands will no longer automatically join to the root of the previous tree, but create disjoint geometry as expected. |
Tue. August 29, 2006 | |
9.0.339 | Triangulate2D's cleanup code is now significantly faster, making triangulating 50k points reasonable and ensuring it is easier to interrupt. |
Tue. August 29, 2006 | |
9.0.339 | Triangulate2D's cleanup code is now significantly faster, making triangulating 50k points reasonable and ensuring it is easier to interrupt. |
Tue. August 29, 2006 | |
9.0.339 | Triangulate2D's cleanup code is now significantly faster, making triangulating 50k points reasonable and ensuring it is easier to interrupt. |
Tue. August 29, 2006 | |
9.0.339 | Triangulate2D's cleanup code is now significantly faster, making triangulating 50k points reasonable and ensuring it is easier to interrupt. |
Tue. August 29, 2006 | |
9.0.339 | Triangulate2D's cleanup code is now significantly faster, making triangulating 50k points reasonable and ensuring it is easier to interrupt. |
Tue. August 29, 2006 | |
9.0.338 | When VEX SOPs evaluate a SOP node reference, such as op:/obj/model/box1, they will now do so at the current cook time of the VEX SOP rather than the global playbar time. This causes them to cook properly when a Cache or Time Shift SOP is used to cook at a different time. A work around for earlier versions is to make the path a parameter to the VEX SOP and use op:/obj/model/box1[$F]. |
Mon. August 28, 2006 | |
9.0.338 | When VEX SOPs evaluate a SOP node reference, such as op:/obj/model/box1, they will now do so at the current cook time of the VEX SOP rather than the global playbar time. This causes them to cook properly when a Cache or Time Shift SOP is used to cook at a different time. A work around for earlier versions is to make the path a parameter to the VEX SOP and use op:/obj/model/box1[$F]. |
Mon. August 28, 2006 | |
9.0.338 | When VEX SOPs evaluate a SOP node reference, such as op:/obj/model/box1, they will now do so at the current cook time of the VEX SOP rather than the global playbar time. This causes them to cook properly when a Cache or Time Shift SOP is used to cook at a different time. A work around for earlier versions is to make the path a parameter to the VEX SOP and use op:/obj/model/box1[$F]. |
Mon. August 28, 2006 | |
9.0.338 | When VEX SOPs evaluate a SOP node reference, such as op:/obj/model/box1, they will now do so at the current cook time of the VEX SOP rather than the global playbar time. This causes them to cook properly when a Cache or Time Shift SOP is used to cook at a different time. A work around for earlier versions is to make the path a parameter to the VEX SOP and use op:/obj/model/box1[$F]. |
Mon. August 28, 2006 | |
9.0.338 | When VEX SOPs evaluate a SOP node reference, such as op:/obj/model/box1, they will now do so at the current cook time of the VEX SOP rather than the global playbar time. This causes them to cook properly when a Cache or Time Shift SOP is used to cook at a different time. A work around for earlier versions is to make the path a parameter to the VEX SOP and use op:/obj/model/box1[$F]. |
Mon. August 28, 2006 | |
9.0.338 | The image3d file format has been updated. To be able to use i3d files generated by a previous version of Houdini, you'll need to run a conversion "i3dconvert -u oldfile newfile" to update each file. |
Mon. August 28, 2006 |