BoundsAdjust

Allows you to adjust the bounding box of a geometry location.

Connection Type

Connection Name

Function

Input

input

The geometry location whose bounding box you want to modify.

 

Control (UI)

Default Value

Function

targetPath

N/A

Describes the location of the geometry who's bounding box is being adjusted. The targetPath parameter options are available in either a scene graph widget or dropdown menu to the right of the parameter.

For more information, refer to the Scene Graph Location Widget Type in the Common Parameter Widgets.

action

Strip Bounds

Sets the type of bounding adjustment to apply:

Strip Bounds - removes the bounding box from the geometry entirely.

Pad Bounds (%) - allows you to pad the bounding box by a user-defined percentage.

Pad Bounds (local) - allows you to pad the bounding box by an amount specified in units.

action: Strip Bounds

stripAncestors

No

Specify whether or not to strip the bound attributes from the ancestor locations.

action: Pad Bounds (%) > padAmount

percentage

0

Specify percentage to add to the original bounding box size. This is a keyable attribute.

adjustAncestors

No

Specify whether or not to expand the bound attributes of any ancestor location to account for the newly adjusted child location bounds.

when

immediate

Sets when the specified adjustment is applied:

immediate - pad the bounds immediately.

deferred - pad the bounds only at render time (more efficient). Padding is calculated in the PRMan plug-in, so the result is not visible in Katana even with implicit resolvers on.

action: Pad Bounds (Local) > padAmount

localSpace

0

Specifies the number of local space units to pad the bounding box.

adjustAncestors

No

Specify whether or not to expand the bound attributes of any ancestor location to account for the newly adjusted child location bounds.

when

immediate

Sets when the specified adjustment is applied:

immediate - pad the bounds immediately.

deferred - pad the bounds only at render time (more efficient). Padding is calculated in the PRMan plug-in, so the result is not visible in Katana even with implicit resolvers on.