Search is based on keyword.
Ex: "Procedures"
Do not search with natural language
Ex: "How do I write a new procedure?"
ScreenCoordinateConstraint
ScreenCoordinateConstraint modifies the camera screen window to fit the target object(s).
Connection Type |
Connection Name |
Function |
Input |
input |
The place in the node graph where you want to constrain the camera screen window to fit the target object. |
Control (UI) |
Default Value |
Function |
basePath |
None |
Sets the object to constrain. The basePath parameter options are available by clicking the dropdown menu. For more information, refer to the Scene Graph Location Widget Type in Common Parameter Widgets. |
targetPath |
None |
Sets the object(s) to which the object in basePath is constrained. The targetPath parameter options are available by clicking Add Locations or dropdown menu. For more information, refer to the Scene Graph Location and Locations Widget Types in Common Parameter Widgets. |
respectMotionBlur |
Yes |
When set to Yes, constraints are adjusted to allow for the target's motion within the time the shutter is open. |
keepAspectRatio |
Yes |
When set to Yes, maintain the aspect ratio of the screen window. When set to No, modify the aspect ratio of the screen window to fill as much of the frame as possible. |
allowMissingTargets |
No |
When set to Yes, silently ignore the constraint if its target is not in the scene graph. When set to No, produce an error on constraint resolution if the target is missing. |
addToConstraintList |
No |
Adds base path to globals.constraintList at /root/world. This is only needed for cases in which one constraint depends on another constraint already being evaluated. The globals.constraintList is used to specify the order of evaluation of constraints. |
setRelativeTargets |
No |
Stores target paths in the scene graph constraint definition as paths relative to the base path. Targets should still be specified as absolute paths in this node's parameters. |
Sorry you didn't find this helpful
Why wasn't this helpful? (check all that apply)
Thanks for your feedback.
If you can't find what you're looking for or you have a workflow question, please try Foundry Support.
If you have any thoughts on how we can improve our learning content, please email the Documentation team using the button below.
Thanks for taking time to give us feedback.