Object subnets and custom object subnets have a new parameter, "Visible Children". This parameter specifies a list of child nodes that should be visible. The value is "*" by default. Any child node which is not listed is hidden (as if it's display flag has been turned off).

Object subnets and custom object subnets have a new parameter, "Visible Children". This parameter specifies a list of child nodes that should be visible. The value is "*" by default. Any child node which is not listed is hidden (as if it's display flag has been turned off).

Object subnets and custom object subnets have a new parameter, "Visible Children". This parameter specifies a list of child nodes that should be visible. The value is "*" by default. Any child node which is not listed is hidden (as if it's display flag has been turned off).

Object subnets and custom object subnets have a new parameter, "Visible Children". This parameter specifies a list of child nodes that should be visible. The value is "*" by default. Any child node which is not listed is hidden (as if it's display flag has been turned off).

String parameters which are set to use !!ch()!! style channel references now automatically convert those references to chs or chsop expressions. This is because the chs expressions have generally better behavior, especially when referencing animated parameters. The !!ch()!! references are not modified for non-animatable string menus, and checkbox and integer menus are also not affected.

String parameters which are set to use !!ch()!! style channel references now automatically convert those references to chs or chsop expressions. This is because the chs expressions have generally better behavior, especially when referencing animated parameters. The !!ch()!! references are not modified for non-animatable string menus, and checkbox and integer menus are also not affected.

String parameters which are set to use !!ch()!! style channel references now automatically convert those references to chs or chsop expressions. This is because the chs expressions have generally better behavior, especially when referencing animated parameters. The !!ch()!! references are not modified for non-animatable string menus, and checkbox and integer menus are also not affected.

String parameters which are set to use !!ch()!! style channel references now automatically convert those references to chs or chsop expressions. This is because the chs expressions have generally better behavior, especially when referencing animated parameters. The !!ch()!! references are not modified for non-animatable string menus, and checkbox and integer menus are also not affected.

String parameters which are set to use !!ch()!! style channel references now automatically convert those references to chs or chsop expressions. This is because the chs expressions have generally better behavior, especially when referencing animated parameters. The !!ch()!! references are not modified for non-animatable string menus, and checkbox and integer menus are also not affected.

String parameters which are set to use !!ch()!! style channel references now automatically convert those references to chs or chsop expressions. This is because the chs expressions have generally better behavior, especially when referencing animated parameters. The !!ch()!! references are not modified for non-animatable string menus, and checkbox and integer menus are also not affected.

Added a new chsop expression function which is similar to the chs expression but is intended for fetching node names. If the fetched node name is a relative path, it is automatically converted to the appropriate absolute path.

Added a new chsop expression function which is similar to the chs expression but is intended for fetching node names. If the fetched node name is a relative path, it is automatically converted to the appropriate absolute path.

Added a new chsop expression function which is similar to the chs expression but is intended for fetching node names. If the fetched node name is a relative path, it is automatically converted to the appropriate absolute path.

Added a new chsop expression function which is similar to the chs expression but is intended for fetching node names. If the fetched node name is a relative path, it is automatically converted to the appropriate absolute path.

Added a new chsop expression function which is similar to the chs expression but is intended for fetching node names. If the fetched node name is a relative path, it is automatically converted to the appropriate absolute path.

Added a new chsop expression function which is similar to the chs expression but is intended for fetching node names. If the fetched node name is a relative path, it is automatically converted to the appropriate absolute path.

Fixed a bug with our automatic updating of expression functions when a node name changes. If the node's name appeared multiple times and within a nested expression, after changing the node name the expression could be mangled. This no longer happens.

Fixed a bug with our automatic updating of expression functions when a node name changes. If the node's name appeared multiple times and within a nested expression, after changing the node name the expression could be mangled. This no longer happens.

Fixed a bug with our automatic updating of expression functions when a node name changes. If the node's name appeared multiple times and within a nested expression, after changing the node name the expression could be mangled. This no longer happens.

Fixed a bug with our automatic updating of expression functions when a node name changes. If the node's name appeared multiple times and within a nested expression, after changing the node name the expression could be mangled. This no longer happens.

Fixed a bug with our automatic updating of expression functions when a node name changes. If the node's name appeared multiple times and within a nested expression, after changing the node name the expression could be mangled. This no longer happens.

Fixed a bug with our automatic updating of expression functions when a node name changes. If the node's name appeared multiple times and within a nested expression, after changing the node name the expression could be mangled. This no longer happens.

The 'ip' render output now has options to:

• start a new sequence in mplay, or write to the current sequence (ifany)
• write frames to their corresponding frame numbers in mplay, or just

append to the end of the sequence.

The default behaviour is to append to the end of the current sequence, which is exactly the same as previous versions. These options can be changed using the Image Options pulldown found below most output drivers' Output Picture parameter.

The 'ip' render output now has options to:

• start a new sequence in mplay, or write to the current sequence (ifany)
• write frames to their corresponding frame numbers in mplay, or just

append to the end of the sequence.

The default behaviour is to append to the end of the current sequence, which is exactly the same as previous versions. These options can be changed using the Image Options pulldown found below most output drivers' Output Picture parameter.

The 'ip' render output now has options to:

• start a new sequence in mplay, or write to the current sequence (ifany)
• write frames to their corresponding frame numbers in mplay, or just

append to the end of the sequence.

The default behaviour is to append to the end of the current sequence, which is exactly the same as previous versions. These options can be changed using the Image Options pulldown found below most output drivers' Output Picture parameter.