Houdini Main Changelogs

7.0.39

you can move keys past other keys on the same channel

Mon. April 12, 2004
7.0.39

Particle networks now have a "Random Seed" parameter to allow reuse of the same network to get differing behaviors.

Mon. April 12, 2004
7.0.39

Particle networks now have a "Random Seed" parameter to allow reuse of the same network to get differing behaviors.

Mon. April 12, 2004
7.0.39

Particle networks now have a "Random Seed" parameter to allow reuse of the same network to get differing behaviors.

Mon. April 12, 2004
7.0.39

Particle networks now have a "Random Seed" parameter to allow reuse of the same network to get differing behaviors.

Mon. April 12, 2004
7.0.39

Particle networks now have a "Random Seed" parameter to allow reuse of the same network to get differing behaviors.

Mon. April 12, 2004
7.0.39

Fixed crash when updating custom operator definitions on existing nodes which had differing parameter lists.

Mon. April 12, 2004
7.0.39

Fixed crash when updating custom operator definitions on existing nodes which had differing parameter lists.

Mon. April 12, 2004
7.0.39

Fixed crash when updating custom operator definitions on existing nodes which had differing parameter lists.

Mon. April 12, 2004
7.0.39

Fixed crash when updating custom operator definitions on existing nodes which had differing parameter lists.

Mon. April 12, 2004
7.0.39

Fixed crash when updating custom operator definitions on existing nodes which had differing parameter lists.

Mon. April 12, 2004
7.0.35

A bug with specifying light scopes inside VEX statements was fixed.

Thu. April 8, 2004
7.0.35

A bug with specifying light scopes inside VEX statements was fixed.

Thu. April 8, 2004
7.0.35

A bug with specifying light scopes inside VEX statements was fixed.

Thu. April 8, 2004
7.0.35

A bug with specifying light scopes inside VEX statements was fixed.

Thu. April 8, 2004
7.0.35

A bug with specifying light scopes inside VEX statements was fixed.

Thu. April 8, 2004
7.0.35

The behaviour of hserver in bad conditions has been improved significantly. As well, applications now have a default grace period to run before they terminate due to license failure. This grace period is only allowed if there was successful license checkout at some point in the past.

hserver will still block on occassion. This is a limitation of the fact that each Houdini application (including hscript, mantra etc.) will connect to hserver at some point in time for license information. If hserver is unable to contact sesinetd on the remote machine, each of these applications will block an hserver thread.

The default number of threads was bumped up from 3 to 6. This allows 5 concurrent applications to block up threads and still be able to run "hserver -l" to query the status of hserver.

Thu. April 8, 2004
7.0.35

The behaviour of hserver in bad conditions has been improved significantly. As well, applications now have a default grace period to run before they terminate due to license failure. This grace period is only allowed if there was successful license checkout at some point in the past.

hserver will still block on occassion. This is a limitation of the fact that each Houdini application (including hscript, mantra etc.) will connect to hserver at some point in time for license information. If hserver is unable to contact sesinetd on the remote machine, each of these applications will block an hserver thread.

The default number of threads was bumped up from 3 to 6. This allows 5 concurrent applications to block up threads and still be able to run "hserver -l" to query the status of hserver.

Thu. April 8, 2004
7.0.35

The behaviour of hserver in bad conditions has been improved significantly. As well, applications now have a default grace period to run before they terminate due to license failure. This grace period is only allowed if there was successful license checkout at some point in the past.

hserver will still block on occassion. This is a limitation of the fact that each Houdini application (including hscript, mantra etc.) will connect to hserver at some point in time for license information. If hserver is unable to contact sesinetd on the remote machine, each of these applications will block an hserver thread.

The default number of threads was bumped up from 3 to 6. This allows 5 concurrent applications to block up threads and still be able to run "hserver -l" to query the status of hserver.

Thu. April 8, 2004
7.0.35

The behaviour of hserver in bad conditions has been improved significantly. As well, applications now have a default grace period to run before they terminate due to license failure. This grace period is only allowed if there was successful license checkout at some point in the past.

hserver will still block on occassion. This is a limitation of the fact that each Houdini application (including hscript, mantra etc.) will connect to hserver at some point in time for license information. If hserver is unable to contact sesinetd on the remote machine, each of these applications will block an hserver thread.

The default number of threads was bumped up from 3 to 6. This allows 5 concurrent applications to block up threads and still be able to run "hserver -l" to query the status of hserver.

Thu. April 8, 2004
7.0.35

The behaviour of hserver in bad conditions has been improved significantly. As well, applications now have a default grace period to run before they terminate due to license failure. This grace period is only allowed if there was successful license checkout at some point in the past.

hserver will still block on occassion. This is a limitation of the fact that each Houdini application (including hscript, mantra etc.) will connect to hserver at some point in time for license information. If hserver is unable to contact sesinetd on the remote machine, each of these applications will block an hserver thread.

The default number of threads was bumped up from 3 to 6. This allows 5 concurrent applications to block up threads and still be able to run "hserver -l" to query the status of hserver.

Thu. April 8, 2004
7.0.34

Split out the Composite COP into specific compositing COPs: Over, Under, Atop, Inside, Outside, Add, Subtract, Multiply, Screen, Diff, Average and Xor.

Wed. April 7, 2004
7.0.34

Split out the Composite COP into specific compositing COPs: Over, Under, Atop, Inside, Outside, Add, Subtract, Multiply, Screen, Diff, Average and Xor.

Wed. April 7, 2004
7.0.34

Split out the Composite COP into specific compositing COPs: Over, Under, Atop, Inside, Outside, Add, Subtract, Multiply, Screen, Diff, Average and Xor.

Wed. April 7, 2004
7.0.34

Split out the Composite COP into specific compositing COPs: Over, Under, Atop, Inside, Outside, Add, Subtract, Multiply, Screen, Diff, Average and Xor.

Wed. April 7, 2004