The ombind command now prevents the user from creating bindings between a manipulator meant for manipulating one type of op, and an op of another type. For example, the transform2d manipulator only works on cop2 nodes. Previously this rule was not enforced in any way. Now it is.

The ombind command now prevents the user from creating bindings between a manipulator meant for manipulating one type of op, and an op of another type. For example, the transform2d manipulator only works on cop2 nodes. Previously this rule was not enforced in any way. Now it is.

The ombind command now prevents the user from creating bindings between a manipulator meant for manipulating one type of op, and an op of another type. For example, the transform2d manipulator only works on cop2 nodes. Previously this rule was not enforced in any way. Now it is.

It is now possible to put non-bone objects into IK bone chains and the IK solver will still generate correct solutions. There will be problems in some situations (such as non-uniform scales and lookat constraints). But now there is a lot more flexibility in allowable bone chain setups.

It is now possible to put non-bone objects into IK bone chains and the IK solver will still generate correct solutions. There will be problems in some situations (such as non-uniform scales and lookat constraints). But now there is a lot more flexibility in allowable bone chain setups.

It is now possible to put non-bone objects into IK bone chains and the IK solver will still generate correct solutions. There will be problems in some situations (such as non-uniform scales and lookat constraints). But now there is a lot more flexibility in allowable bone chain setups.

It is now possible to put non-bone objects into IK bone chains and the IK solver will still generate correct solutions. There will be problems in some situations (such as non-uniform scales and lookat constraints). But now there is a lot more flexibility in allowable bone chain setups.

It is now possible to put non-bone objects into IK bone chains and the IK solver will still generate correct solutions. There will be problems in some situations (such as non-uniform scales and lookat constraints). But now there is a lot more flexibility in allowable bone chain setups.

Character workflow improvements:

• The Edit Capture Regions state now has an option to always update

your capture information. This means that you can edit your capture regions without being at the capture frame to see your weighting if they haven't been keyframed.

• The Capture Geometry state will now prompt the user to remove keysat the old capture frame when recapturing. This provides an easymethod for moving your capture frame when you haven't locked yourcapture SOP. If you've locked your capture SOP, then you don't careabout the capture frame anyways.
• The Capture Geometry state will now always create channel groups forthe keys that it creates at the capture frame. You can also specifythe prefix of the channel groups.
• The CaptureEdit SOP no longer has a capture frame parameter. TheCapture/ProximityCapture SOPs now create a detail attribute namedpCaptFrame that the CaptureEdit SOP will use instead. This meansthat the workflow has been improved so that you only have to worryabout the capture frame in the Capture Geometry state.

Character workflow improvements:

• The Edit Capture Regions state now has an option to always update

your capture information. This means that you can edit your capture regions without being at the capture frame to see your weighting if they haven't been keyframed.

• The Capture Geometry state will now prompt the user to remove keysat the old capture frame when recapturing. This provides an easymethod for moving your capture frame when you haven't locked yourcapture SOP. If you've locked your capture SOP, then you don't careabout the capture frame anyways.
• The Capture Geometry state will now always create channel groups forthe keys that it creates at the capture frame. You can also specifythe prefix of the channel groups.
• The CaptureEdit SOP no longer has a capture frame parameter. TheCapture/ProximityCapture SOPs now create a detail attribute namedpCaptFrame that the CaptureEdit SOP will use instead. This meansthat the workflow has been improved so that you only have to worryabout the capture frame in the Capture Geometry state.

Character workflow improvements:

• The Edit Capture Regions state now has an option to always update

your capture information. This means that you can edit your capture regions without being at the capture frame to see your weighting if they haven't been keyframed.

• The Capture Geometry state will now prompt the user to remove keysat the old capture frame when recapturing. This provides an easymethod for moving your capture frame when you haven't locked yourcapture SOP. If you've locked your capture SOP, then you don't careabout the capture frame anyways.
• The Capture Geometry state will now always create channel groups forthe keys that it creates at the capture frame. You can also specifythe prefix of the channel groups.
• The CaptureEdit SOP no longer has a capture frame parameter. TheCapture/ProximityCapture SOPs now create a detail attribute namedpCaptFrame that the CaptureEdit SOP will use instead. This meansthat the workflow has been improved so that you only have to worryabout the capture frame in the Capture Geometry state.

Character workflow improvements:

• The Edit Capture Regions state now has an option to always update

your capture information. This means that you can edit your capture regions without being at the capture frame to see your weighting if they haven't been keyframed.

• The Capture Geometry state will now prompt the user to remove keysat the old capture frame when recapturing. This provides an easymethod for moving your capture frame when you haven't locked yourcapture SOP. If you've locked your capture SOP, then you don't careabout the capture frame anyways.
• The Capture Geometry state will now always create channel groups forthe keys that it creates at the capture frame. You can also specifythe prefix of the channel groups.
• The CaptureEdit SOP no longer has a capture frame parameter. TheCapture/ProximityCapture SOPs now create a detail attribute namedpCaptFrame that the CaptureEdit SOP will use instead. This meansthat the workflow has been improved so that you only have to worryabout the capture frame in the Capture Geometry state.

Character workflow improvements:

• The Edit Capture Regions state now has an option to always update

your capture information. This means that you can edit your capture regions without being at the capture frame to see your weighting if they haven't been keyframed.

• The Capture Geometry state will now prompt the user to remove keysat the old capture frame when recapturing. This provides an easymethod for moving your capture frame when you haven't locked yourcapture SOP. If you've locked your capture SOP, then you don't careabout the capture frame anyways.
• The Capture Geometry state will now always create channel groups forthe keys that it creates at the capture frame. You can also specifythe prefix of the channel groups.
• The CaptureEdit SOP no longer has a capture frame parameter. TheCapture/ProximityCapture SOPs now create a detail attribute namedpCaptFrame that the CaptureEdit SOP will use instead. This meansthat the workflow has been improved so that you only have to worryabout the capture frame in the Capture Geometry state.

Added hotkey for editing snap options.

Added hotkey for editing snap options.

Added hotkey for editing snap options.

Added hotkey for editing snap options.

Added hotkey for editing snap options.

The Field COP now does Pullup and Pulldown, for any film and video rates.

The Field COP now does Pullup and Pulldown, for any film and video rates.

The Field COP now does Pullup and Pulldown, for any film and video rates.

The Field COP now does Pullup and Pulldown, for any film and video rates.

The Field COP now does Pullup and Pulldown, for any film and video rates.

Polysplit should now do the "auto-close" with more accuracy than before. Before it use to compare the 3D points of the objects, now it compares the distances between their projected points in screen space.

Polysplit should now do the "auto-close" with more accuracy than before. Before it use to compare the 3D points of the objects, now it compares the distances between their projected points in screen space.