Houdini Main Changelogs
![]() |
7.0.22 | Fixed crash on exiting CaptureLayerPaint state. |
金. 3月 26, 2004 |
![]() |
7.0.22 | Fixed crash on exiting CaptureLayerPaint state. |
金. 3月 26, 2004 |
![]() |
7.0.22 | Fixed crash on exiting CaptureLayerPaint state. |
金. 3月 26, 2004 |
![]() |
7.0.22 | Fixed crash on exiting CaptureLayerPaint state. |
金. 3月 26, 2004 |
![]() |
7.0.22 | Fixed crash on exiting CaptureLayerPaint state. |
金. 3月 26, 2004 |
![]() |
7.0.22 | Fixed crash on exiting CaptureLayerPaint state. |
金. 3月 26, 2004 |
![]() |
7.0.22 | Renamed EditPoints state to Morph. |
金. 3月 26, 2004 |
![]() |
7.0.22 | Renamed EditPoints state to Morph. |
金. 3月 26, 2004 |
![]() |
7.0.22 | Renamed EditPoints state to Morph. |
金. 3月 26, 2004 |
![]() |
7.0.22 | Renamed EditPoints state to Morph. |
金. 3月 26, 2004 |
![]() |
7.0.22 | Renamed EditPoints state to Morph. |
金. 3月 26, 2004 |
![]() |
7.0.22 | Renamed EditPoints state to Morph. |
金. 3月 26, 2004 |
![]() |
7.0.21 | Removing the hconnect proto install. Since openport/hcommand now uses sockets and can work with telnet, hconnect is no longer needed. |
木. 3月 25, 2004 |
![]() |
7.0.21 | Removing the hconnect proto install. Since openport/hcommand now uses sockets and can work with telnet, hconnect is no longer needed. |
木. 3月 25, 2004 |
![]() |
7.0.21 | Removing the hconnect proto install. Since openport/hcommand now uses sockets and can work with telnet, hconnect is no longer needed. |
木. 3月 25, 2004 |
![]() |
7.0.21 | Removing the hconnect proto install. Since openport/hcommand now uses sockets and can work with telnet, hconnect is no longer needed. |
木. 3月 25, 2004 |
![]() |
7.0.21 | Removing the hconnect proto install. Since openport/hcommand now uses sockets and can work with telnet, hconnect is no longer needed. |
木. 3月 25, 2004 |
![]() |
7.0.21 | Removing the hconnect proto install. Since openport/hcommand now uses sockets and can work with telnet, hconnect is no longer needed. |
木. 3月 25, 2004 |
![]() |
7.0.21 | The openport command and hcommand now use sockets instead of message queues to communicate. This way, if Houdini is killed, message queues are not left lying around. Also, the system limit for sockets is much higher than for message queues, so it's possible to have more ports open at once. The help browser and the java, tcl and tk commands now also use sockets to run commands in Houdini. As a consequence, it is now possible to use openport across machines. By default, the openport command only allows connections from the local machine, but other hosts can be allowed to connect by specifying an IP mask when the port is opened. Also, it is now possible to telnet to an open port to run Houdini commands. Note that ports numbers less than 10000 use a socket port that is 10000 greater than the Houdini port number. |
木. 3月 25, 2004 |
![]() |
7.0.21 | The openport command and hcommand now use sockets instead of message queues to communicate. This way, if Houdini is killed, message queues are not left lying around. Also, the system limit for sockets is much higher than for message queues, so it's possible to have more ports open at once. The help browser and the java, tcl and tk commands now also use sockets to run commands in Houdini. As a consequence, it is now possible to use openport across machines. By default, the openport command only allows connections from the local machine, but other hosts can be allowed to connect by specifying an IP mask when the port is opened. Also, it is now possible to telnet to an open port to run Houdini commands. Note that ports numbers less than 10000 use a socket port that is 10000 greater than the Houdini port number. |
木. 3月 25, 2004 |
![]() |
7.0.21 | The openport command and hcommand now use sockets instead of message queues to communicate. This way, if Houdini is killed, message queues are not left lying around. Also, the system limit for sockets is much higher than for message queues, so it's possible to have more ports open at once. The help browser and the java, tcl and tk commands now also use sockets to run commands in Houdini. As a consequence, it is now possible to use openport across machines. By default, the openport command only allows connections from the local machine, but other hosts can be allowed to connect by specifying an IP mask when the port is opened. Also, it is now possible to telnet to an open port to run Houdini commands. Note that ports numbers less than 10000 use a socket port that is 10000 greater than the Houdini port number. |
木. 3月 25, 2004 |
![]() |
7.0.21 | The openport command and hcommand now use sockets instead of message queues to communicate. This way, if Houdini is killed, message queues are not left lying around. Also, the system limit for sockets is much higher than for message queues, so it's possible to have more ports open at once. The help browser and the java, tcl and tk commands now also use sockets to run commands in Houdini. As a consequence, it is now possible to use openport across machines. By default, the openport command only allows connections from the local machine, but other hosts can be allowed to connect by specifying an IP mask when the port is opened. Also, it is now possible to telnet to an open port to run Houdini commands. Note that ports numbers less than 10000 use a socket port that is 10000 greater than the Houdini port number. |
木. 3月 25, 2004 |
![]() |
7.0.21 | The openport command and hcommand now use sockets instead of message queues to communicate. This way, if Houdini is killed, message queues are not left lying around. Also, the system limit for sockets is much higher than for message queues, so it's possible to have more ports open at once. The help browser and the java, tcl and tk commands now also use sockets to run commands in Houdini. As a consequence, it is now possible to use openport across machines. By default, the openport command only allows connections from the local machine, but other hosts can be allowed to connect by specifying an IP mask when the port is opened. Also, it is now possible to telnet to an open port to run Houdini commands. Note that ports numbers less than 10000 use a socket port that is 10000 greater than the Houdini port number. |
木. 3月 25, 2004 |
![]() |
7.0.21 | The openport command and hcommand now use sockets instead of message queues to communicate. This way, if Houdini is killed, message queues are not left lying around. Also, the system limit for sockets is much higher than for message queues, so it's possible to have more ports open at once. The help browser and the java, tcl and tk commands now also use sockets to run commands in Houdini. As a consequence, it is now possible to use openport across machines. By default, the openport command only allows connections from the local machine, but other hosts can be allowed to connect by specifying an IP mask when the port is opened. Also, it is now possible to telnet to an open port to run Houdini commands. Note that ports numbers less than 10000 use a socket port that is 10000 greater than the Houdini port number. |
木. 3月 25, 2004 |
![]() |
7.0.21 | The PaintCaptureLayer state can now switch between any CaptureLayerPaint SOP feeding into the displayed SOP. The state can also visualize the final capture weights used in a deform. |
木. 3月 25, 2004 |