Undoing a rename operation on a locked subnet operator type could cause the expressions of the nodes inside the subnet to be erased. This problem is now fixed.

Undoing a rename operation on a locked subnet operator type could cause the expressions of the nodes inside the subnet to be erased. This problem is now fixed.

Undoing a rename operation on a locked subnet operator type could cause the expressions of the nodes inside the subnet to be erased. This problem is now fixed.

Fixed a problem with channel referencing a parameter of a node that is not cooked (such as an object that isn't displayed). Suppose geo1, geo2, and geo3 are all objects. geo2 is not displayed. geo2/tx is 'ch("../geo1/tx")' and geo3/tx is 'ch("../geo2/tx")'. Changing geo1/tx would not move geo3 because geo2 would not cook and so would not propagate the parameter change. This problem is now fixed.

Fixed a problem with channel referencing a parameter of a node that is not cooked (such as an object that isn't displayed). Suppose geo1, geo2, and geo3 are all objects. geo2 is not displayed. geo2/tx is 'ch("../geo1/tx")' and geo3/tx is 'ch("../geo2/tx")'. Changing geo1/tx would not move geo3 because geo2 would not cook and so would not propagate the parameter change. This problem is now fixed.

Fixed a problem with channel referencing a parameter of a node that is not cooked (such as an object that isn't displayed). Suppose geo1, geo2, and geo3 are all objects. geo2 is not displayed. geo2/tx is 'ch("../geo1/tx")' and geo3/tx is 'ch("../geo2/tx")'. Changing geo1/tx would not move geo3 because geo2 would not cook and so would not propagate the parameter change. This problem is now fixed.

Fixed a problem with channel referencing a parameter of a node that is not cooked (such as an object that isn't displayed). Suppose geo1, geo2, and geo3 are all objects. geo2 is not displayed. geo2/tx is 'ch("../geo1/tx")' and geo3/tx is 'ch("../geo2/tx")'. Changing geo1/tx would not move geo3 because geo2 would not cook and so would not propagate the parameter change. This problem is now fixed.

Fixed a problem with channel referencing a parameter of a node that is not cooked (such as an object that isn't displayed). Suppose geo1, geo2, and geo3 are all objects. geo2 is not displayed. geo2/tx is 'ch("../geo1/tx")' and geo3/tx is 'ch("../geo2/tx")'. Changing geo1/tx would not move geo3 because geo2 would not cook and so would not propagate the parameter change. This problem is now fixed.

When a parameter uses a channel reference with th "!!ch()!!" format, the parameter is marked with a green dot in the parameter dialog. This makes it easy to detect parameters using this sort of channel reference.

When a parameter uses a channel reference with th "!!ch()!!" format, the parameter is marked with a green dot in the parameter dialog. This makes it easy to detect parameters using this sort of channel reference.

When a parameter uses a channel reference with th "!!ch()!!" format, the parameter is marked with a green dot in the parameter dialog. This makes it easy to detect parameters using this sort of channel reference.

When a parameter uses a channel reference with th "!!ch()!!" format, the parameter is marked with a green dot in the parameter dialog. This makes it easy to detect parameters using this sort of channel reference.

When a parameter uses a channel reference with th "!!ch()!!" format, the parameter is marked with a green dot in the parameter dialog. This makes it easy to detect parameters using this sort of channel reference.

The Sticky objects now have a reasonable selector which prompts for object to stick to. They thing prompt to move the sticky by clicking on the object.

Infinite recursion of the sticky space transforms is now detected and properly errored.

The Sticky objects now have a reasonable selector which prompts for object to stick to. They thing prompt to move the sticky by clicking on the object.

Infinite recursion of the sticky space transforms is now detected and properly errored.

The Sticky objects now have a reasonable selector which prompts for object to stick to. They thing prompt to move the sticky by clicking on the object.

Infinite recursion of the sticky space transforms is now detected and properly errored.

The Sticky objects now have a reasonable selector which prompts for object to stick to. They thing prompt to move the sticky by clicking on the object.

Infinite recursion of the sticky space transforms is now detected and properly errored.

The Sticky objects now have a reasonable selector which prompts for object to stick to. They thing prompt to move the sticky by clicking on the object.

Infinite recursion of the sticky space transforms is now detected and properly errored.

Transform spaces are output for null objects if and only if the null object is "displayed". That is, if the display flag of the null object is turned off, or the null object doesn't match the visible objects pattern, a transform space will not be declared in RIB or IFD streams.

Transform spaces are output for null objects if and only if the null object is "displayed". That is, if the display flag of the null object is turned off, or the null object doesn't match the visible objects pattern, a transform space will not be declared in RIB or IFD streams.