Houdini Main Changelogs
6.0.203 | It is now possible to create scripted subnet operator types with more than four inputs. |
Thu. February 6, 2003 | |
6.0.203 | It is now possible to create scripted subnet operator types with more than four inputs. |
Thu. February 6, 2003 | |
6.0.203 | It is now possible to create scripted subnet operator types with more than four inputs. |
Thu. February 6, 2003 | |
6.0.203 | When loading a unknown COP2, ROP, or VOP operator type, Houdini would stop loading the file. Now it creates a default operator in place of the unknown operator type and continues loading. This is the behavior that already was in place for all other operator types. |
Thu. February 6, 2003 | |
6.0.203 | When loading a unknown COP2, ROP, or VOP operator type, Houdini would stop loading the file. Now it creates a default operator in place of the unknown operator type and continues loading. This is the behavior that already was in place for all other operator types. |
Thu. February 6, 2003 | |
6.0.203 | When loading a unknown COP2, ROP, or VOP operator type, Houdini would stop loading the file. Now it creates a default operator in place of the unknown operator type and continues loading. This is the behavior that already was in place for all other operator types. |
Thu. February 6, 2003 | |
6.0.203 | When loading a unknown COP2, ROP, or VOP operator type, Houdini would stop loading the file. Now it creates a default operator in place of the unknown operator type and continues loading. This is the behavior that already was in place for all other operator types. |
Thu. February 6, 2003 | |
6.0.203 | When loading a unknown COP2, ROP, or VOP operator type, Houdini would stop loading the file. Now it creates a default operator in place of the unknown operator type and continues loading. This is the behavior that already was in place for all other operator types. |
Thu. February 6, 2003 | |
6.0.203 | The ROP Output Driver COP2 Node allows an output driver for COP2 to be placed directly in the network. This allows halo users to avoid needing to change networks. |
Thu. February 6, 2003 | |
6.0.203 | The ROP Output Driver COP2 Node allows an output driver for COP2 to be placed directly in the network. This allows halo users to avoid needing to change networks. |
Thu. February 6, 2003 | |
6.0.203 | The ROP Output Driver COP2 Node allows an output driver for COP2 to be placed directly in the network. This allows halo users to avoid needing to change networks. |
Thu. February 6, 2003 | |
6.0.203 | The ROP Output Driver COP2 Node allows an output driver for COP2 to be placed directly in the network. This allows halo users to avoid needing to change networks. |
Thu. February 6, 2003 | |
6.0.203 | The ROP Output Driver COP2 Node allows an output driver for COP2 to be placed directly in the network. This allows halo users to avoid needing to change networks. |
Thu. February 6, 2003 | |
6.0.203 | The Type Properties...::Parameters page now has an Invisible option for parameters. This allows certain parameters to be marked as invisible so they do not appear in the UI. They can still have handles bound to them, or drive expressions. |
Thu. February 6, 2003 | |
6.0.203 | The Type Properties...::Parameters page now has an Invisible option for parameters. This allows certain parameters to be marked as invisible so they do not appear in the UI. They can still have handles bound to them, or drive expressions. |
Thu. February 6, 2003 | |
6.0.203 | The Type Properties...::Parameters page now has an Invisible option for parameters. This allows certain parameters to be marked as invisible so they do not appear in the UI. They can still have handles bound to them, or drive expressions. |
Thu. February 6, 2003 | |
6.0.203 | The Type Properties...::Parameters page now has an Invisible option for parameters. This allows certain parameters to be marked as invisible so they do not appear in the UI. They can still have handles bound to them, or drive expressions. |
Thu. February 6, 2003 | |
6.0.203 | The Type Properties...::Parameters page now has an Invisible option for parameters. This allows certain parameters to be marked as invisible so they do not appear in the UI. They can still have handles bound to them, or drive expressions. |
Thu. February 6, 2003 | |
6.0.203 | It is now possible to create a new VOP Type from a SHOP or VEX Operator which has exported parameters. Previsouly, doing this would generate an invalid VOP. Now, the generated VOP works properly, and also provides an output connectino for each exported parameter. |
Thu. February 6, 2003 | |
6.0.203 | It is now possible to create a new VOP Type from a SHOP or VEX Operator which has exported parameters. Previsouly, doing this would generate an invalid VOP. Now, the generated VOP works properly, and also provides an output connectino for each exported parameter. |
Thu. February 6, 2003 | |
6.0.203 | It is now possible to create a new VOP Type from a SHOP or VEX Operator which has exported parameters. Previsouly, doing this would generate an invalid VOP. Now, the generated VOP works properly, and also provides an output connectino for each exported parameter. |
Thu. February 6, 2003 | |
6.0.203 | It is now possible to create a new VOP Type from a SHOP or VEX Operator which has exported parameters. Previsouly, doing this would generate an invalid VOP. Now, the generated VOP works properly, and also provides an output connectino for each exported parameter. |
Thu. February 6, 2003 | |
6.0.203 | It is now possible to create a new VOP Type from a SHOP or VEX Operator which has exported parameters. Previsouly, doing this would generate an invalid VOP. Now, the generated VOP works properly, and also provides an output connectino for each exported parameter. |
Thu. February 6, 2003 | |
6.0.202 | New Occlusion and Irradiance VOPs in the surface and light contexts. |
Wed. February 5, 2003 | |
6.0.202 | New Occlusion and Irradiance VOPs in the surface and light contexts. |
Wed. February 5, 2003 |