Houdini Main Changelogs

6.1.7

Fixed bug in the colorreplace and chromakey COPs preventing a hue range of 0-360 from working properly. Also fixed a in colorreplace when using the hue of an achromatic color, which was causing bad values.

Wed. May 7, 2003
6.1.7

Fixed bug in the colorreplace and chromakey COPs preventing a hue range of 0-360 from working properly. Also fixed a in colorreplace when using the hue of an achromatic color, which was causing bad values.

Wed. May 7, 2003
6.1.7

Fixed bug in the colorreplace and chromakey COPs preventing a hue range of 0-360 from working properly. Also fixed a in colorreplace when using the hue of an achromatic color, which was causing bad values.

Wed. May 7, 2003
6.1.7

Fixed bug in the colorreplace and chromakey COPs preventing a hue range of 0-360 from working properly. Also fixed a in colorreplace when using the hue of an achromatic color, which was causing bad values.

Wed. May 7, 2003
6.1.7

Fixed bug where if you scoped 97 channels in the dopesheet and then scroll to the bottom, you will notice that the rows become off by 1 with the names.

Wed. May 7, 2003
6.1.7

Fixed bug where if you scoped 97 channels in the dopesheet and then scroll to the bottom, you will notice that the rows become off by 1 with the names.

Wed. May 7, 2003
6.1.7

Fixed bug where if you scoped 97 channels in the dopesheet and then scroll to the bottom, you will notice that the rows become off by 1 with the names.

Wed. May 7, 2003
6.1.7

Fixed bug where if you scoped 97 channels in the dopesheet and then scroll to the bottom, you will notice that the rows become off by 1 with the names.

Wed. May 7, 2003
6.1.7

Fixed bug where if you scoped 97 channels in the dopesheet and then scroll to the bottom, you will notice that the rows become off by 1 with the names.

Wed. May 7, 2003
6.1.7

When saving a subnet operator type definition from the Type Properties dialog, we now check all CHOP nodes contained in the subnet to ensure that any exports specified in the CHOP Exporter dialog export to nodes contained in the subnet, and do so using relative paths. Absolute paths are automatically converted to relative paths, and warnings are generated if any possible problems are found.

Wed. May 7, 2003
6.1.7

When saving a subnet operator type definition from the Type Properties dialog, we now check all CHOP nodes contained in the subnet to ensure that any exports specified in the CHOP Exporter dialog export to nodes contained in the subnet, and do so using relative paths. Absolute paths are automatically converted to relative paths, and warnings are generated if any possible problems are found.

Wed. May 7, 2003
6.1.7

When saving a subnet operator type definition from the Type Properties dialog, we now check all CHOP nodes contained in the subnet to ensure that any exports specified in the CHOP Exporter dialog export to nodes contained in the subnet, and do so using relative paths. Absolute paths are automatically converted to relative paths, and warnings are generated if any possible problems are found.

Wed. May 7, 2003
6.1.7

When saving a subnet operator type definition from the Type Properties dialog, we now check all CHOP nodes contained in the subnet to ensure that any exports specified in the CHOP Exporter dialog export to nodes contained in the subnet, and do so using relative paths. Absolute paths are automatically converted to relative paths, and warnings are generated if any possible problems are found.

Wed. May 7, 2003
6.1.7

When saving a subnet operator type definition from the Type Properties dialog, we now check all CHOP nodes contained in the subnet to ensure that any exports specified in the CHOP Exporter dialog export to nodes contained in the subnet, and do so using relative paths. Absolute paths are automatically converted to relative paths, and warnings are generated if any possible problems are found.

Wed. May 7, 2003
6.1.6

In the SOP/POP contexts, there is now a function computenormal() which determines the behaviour of the N attribute at the conclusion of the cook. Please see on-line VEX documents for more information.

Tue. May 6, 2003
6.1.6

In the SOP/POP contexts, there is now a function computenormal() which determines the behaviour of the N attribute at the conclusion of the cook. Please see on-line VEX documents for more information.

Tue. May 6, 2003
6.1.6

In the SOP/POP contexts, there is now a function computenormal() which determines the behaviour of the N attribute at the conclusion of the cook. Please see on-line VEX documents for more information.

Tue. May 6, 2003
6.1.6

In the SOP/POP contexts, there is now a function computenormal() which determines the behaviour of the N attribute at the conclusion of the cook. Please see on-line VEX documents for more information.

Tue. May 6, 2003
6.1.6

In the SOP/POP contexts, there is now a function computenormal() which determines the behaviour of the N attribute at the conclusion of the cook. Please see on-line VEX documents for more information.

Tue. May 6, 2003
6.1.6

When the alpha para/perp parameters had the same value, they were ignored by the layered surface shader. This has been fixed, which may change the appearance of existing instances of the layered surface shader which have the same non-one values for apara and aperp.

Tue. May 6, 2003
6.1.6

When the alpha para/perp parameters had the same value, they were ignored by the layered surface shader. This has been fixed, which may change the appearance of existing instances of the layered surface shader which have the same non-one values for apara and aperp.

Tue. May 6, 2003
6.1.6

When the alpha para/perp parameters had the same value, they were ignored by the layered surface shader. This has been fixed, which may change the appearance of existing instances of the layered surface shader which have the same non-one values for apara and aperp.

Tue. May 6, 2003
6.1.6

When the alpha para/perp parameters had the same value, they were ignored by the layered surface shader. This has been fixed, which may change the appearance of existing instances of the layered surface shader which have the same non-one values for apara and aperp.

Tue. May 6, 2003
6.1.6

When the alpha para/perp parameters had the same value, they were ignored by the layered surface shader. This has been fixed, which may change the appearance of existing instances of the layered surface shader which have the same non-one values for apara and aperp.

Tue. May 6, 2003
6.1.6

When the alpha para and alpha perp values were the same value, the layered surface shader incorrectly ignored their values. This has been fixed.

Tue. May 6, 2003