Houdini Main Changelogs
5.5.15 | It is now possible for mantra to render sub-division surfaces and points from disk files (bounded or otherwise). |
Fri. June 7, 2002 | |
5.5.15 | It is now possible for mantra to render sub-division surfaces and points from disk files (bounded or otherwise). |
Fri. June 7, 2002 | |
5.5.15 | The Houdini License Administrator can now display licensing diagnostic information. This information can be saved to a file and emailed to Side Effects Software to help resolve licensing problems. |
Fri. June 7, 2002 | |
5.5.15 | The Houdini License Administrator can now display licensing diagnostic information. This information can be saved to a file and emailed to Side Effects Software to help resolve licensing problems. |
Fri. June 7, 2002 | |
5.5.15 | The Houdini License Administrator can now display licensing diagnostic information. This information can be saved to a file and emailed to Side Effects Software to help resolve licensing problems. |
Fri. June 7, 2002 | |
5.5.15 | The Houdini License Administrator can now display licensing diagnostic information. This information can be saved to a file and emailed to Side Effects Software to help resolve licensing problems. |
Fri. June 7, 2002 | |
5.5.15 | The Houdini License Administrator can now display licensing diagnostic information. This information can be saved to a file and emailed to Side Effects Software to help resolve licensing problems. |
Fri. June 7, 2002 | |
5.5.15 | Offset MMB menu on inputs for VOPs to prevent annoying accidental selections and creations of nodes. |
Fri. June 7, 2002 | |
5.5.15 | Offset MMB menu on inputs for VOPs to prevent annoying accidental selections and creations of nodes. |
Fri. June 7, 2002 | |
5.5.15 | Offset MMB menu on inputs for VOPs to prevent annoying accidental selections and creations of nodes. |
Fri. June 7, 2002 | |
5.5.15 | Offset MMB menu on inputs for VOPs to prevent annoying accidental selections and creations of nodes. |
Fri. June 7, 2002 | |
5.5.15 | Offset MMB menu on inputs for VOPs to prevent annoying accidental selections and creations of nodes. |
Fri. June 7, 2002 | |
5.5.14 | Fixed problem where the interrupt dialog was sometimes popping up without the Interrupt button on it. |
Thu. June 6, 2002 | |
5.5.14 | Fixed problem where the interrupt dialog was sometimes popping up without the Interrupt button on it. |
Thu. June 6, 2002 | |
5.5.14 | Fixed problem where the interrupt dialog was sometimes popping up without the Interrupt button on it. |
Thu. June 6, 2002 | |
5.5.14 | Fixed problem where the interrupt dialog was sometimes popping up without the Interrupt button on it. |
Thu. June 6, 2002 | |
5.5.14 | Fixed problem where the interrupt dialog was sometimes popping up without the Interrupt button on it. |
Thu. June 6, 2002 | |
5.5.14 | Fixed some bugs with the rendering of connections while wiring nodes together in the case of horizontally connected ops. |
Thu. June 6, 2002 | |
5.5.14 | Fixed some bugs with the rendering of connections while wiring nodes together in the case of horizontally connected ops. |
Thu. June 6, 2002 | |
5.5.14 | Fixed some bugs with the rendering of connections while wiring nodes together in the case of horizontally connected ops. |
Thu. June 6, 2002 | |
5.5.14 | Fixed some bugs with the rendering of connections while wiring nodes together in the case of horizontally connected ops. |
Thu. June 6, 2002 | |
5.5.14 | Fixed some bugs with the rendering of connections while wiring nodes together in the case of horizontally connected ops. |
Thu. June 6, 2002 | |
5.5.14 | Fixed a bug in VOP code generation where VOPs would output their code in the wrong order. This could result in incorrect visual results, or in VEX compiler errors when using the VOPNET code. |
Thu. June 6, 2002 | |
5.5.14 | Fixed a bug in VOP code generation where VOPs would output their code in the wrong order. This could result in incorrect visual results, or in VEX compiler errors when using the VOPNET code. |
Thu. June 6, 2002 | |
5.5.14 | Fixed a bug in VOP code generation where VOPs would output their code in the wrong order. This could result in incorrect visual results, or in VEX compiler errors when using the VOPNET code. |
Thu. June 6, 2002 |