| On this page | |
| Since | 12.0 |
The Cone Twist Constraint Relationship DOP is one of several constraint
relationship data types. These constraint relationships are attached as
subdata to a 
Constraint DOP node to control the
relationship between the Anchor nodes attached to the Constraint.
A Cone Twist Constraint Relationship is similar to a 
Hard Constraint
Relationship, but specifies an elliptical cone
within which rotation may take place. The cone is described by
specifying a maximum rotation on each axis.
This constraint type is currently only supported by the 
Bullet solver.
Parameters ¶
Data Options ¶
Enable Soft Constraint
When enabled, the position limits, rotation limits, and motor target are treated as soft constraints with individual Stiffness and Damping Ratio parameters. This is primarily useful for following an animated Target Rotation or Target Position in a spring-like manner (e.g. for a ragdoll with target animation), but also allows the position or rotation limits to behave as softer boundaries by decreasing their stiffness.
Max Twist
The maximum twist in degrees.
Max Out Rotation
The maximum rotation from side to side in degrees.
Max Up Rotation
The maximum rotation up or down in degrees.
Softness
Once an angle is greater than softness * the maximum angle, the constraint begins to take effect. Lowering the value of softness softens the constraint boundaries.
Allow Initial Violation of Limits
If the rotation limits are initially violated, the limits will not be enforced but further rotation will be prevented. This allows the objects to naturally move back within the rotation limits, instead of introducing sudden motion at the beginning of the simulation.
Constraint Force Mixing
Increase this to make the constraint spongier, and potentially increase the stability of the simulation. The angular component of the constraint may be violated by an amount proportional to the force required to re-establish the constraint, times this parameter.
Bias Factor
The rate at which the constraint corrects errors in orientation. A value of 1 will ensure that the constraint is always obeyed. It is recommended to keep bias between 0.2 and 0.5.
Relaxation Factor
The rate at which the angular velocity is changed by the constraint. A low value means the constraint will modify the velocities slowly, leaving the boundaries appearing softer.
Angular Limit Stiffness
Specifies the strength of the force that attempts to enforce rotation limits. This value is equivalent to the frequency of a spring.
Angular Limit Damping Ratio
Specifies how much damping is applied to the motion when enforcing rotation limits. This value is equivalent to the damping ratio of a spring. A value of 0 specifies no damping, and a value of 1 provides just enough damping to prevent oscillation. Values between 0 and 1 allow oscillation (with some damping), and values greater than 1 provide increasingly damped motion that has no oscillation.
Twist Translation Range
Specifies the minimum and maximum translation of the constrained object along the Goal Twist Axis.
Out Translation Range
Specifies the minimum and maximum translation of the constrained object along the Goal Out Axis.
Up Translation Range
Specifies the minimum and maximum translation of the constrained object along the Goal Up Axis.
Position CFM
Increase this to make the constraint spongier, and potentially increase the stability of the simulation. The position component of the constraint may be violated by an amount proportional to the force required to re-establish the constraint, times this parameter.
Position ERP
Specifies what proportion of the position error will be fixed during the next simulation step. A value between 0.1 and 0.8 is recommended for most simulation.
Position Limit Stiffness
Specifies the strength of the force that attempts to enforce position limits. This value is equivalent to the frequency of a spring.
Position Limit Damping Ratio
Specifies how much damping is applied to the motion when enforcing position limits. This value is equivalent to the damping ratio of a spring. A value of 0 specifies no damping, and a value of 1 provides just enough damping to prevent oscillation. Values between 0 and 1 allow oscillation (with some damping), and values greater than 1 provide increasingly damped motion that has no oscillation.
Goal Twist Axis
The goal direction of the cone. Defaults to the X axis.
Goal Up Axis
The goal direction of the up axis. Defaults to the Y axis. This should be perpendicular to the twist axis. The out axis is calculated as the cross product of the twist and up axes.
Constrained Twist Axis
The initial twist axis of the constrained object.
Constrained Up Axis
The initial up axis of the constrained object. This should be perpendicular to the constrained twist axis.
Enable Motor
If enabled, the constraint will attempt to also guide the constrained object to a target orientation and position within the rotation limits.
Target Current Pose
The target position and orientation will continually be set to the current relative transform, similar to plasticity. This can be used to add resistance to changes in the relative orientation (controlled by the Target Angular Stiffness or Max Impulse) when there isn’t a specific target.
Target Rotation
Specifies the target orientation (relative to the goal anchor) that the motor should attempt to achieve.
Target Position
Specifies the target position (in the space of the goal anchor) that the motor should attempt to achieve. This position is in the local space of the goal anchor, where X is the Goal Twist Axis, Y is the Goal Out Axis, and Z is the Goal Up Axis.
Use Previous Target
Optionally specifies the motor target at the beginning of the timestep. The solver will interpolate the motor target at each substep for more accurate behavior when the motor target is animated.
Initial Target Rotation
Specifies the Target Rotation at the beginning of the timestep.
Initial Target Position
Specifies the Target Position at the beginning of the timestep.
Ignore Mass
Factors out the mass of the objects when setting the Max Impulse for the constraint. This makes it simpler to set up motors with a similar strength for different pairs of objects.
Max Impulse
Specifies the maximum impulse that the constraint solver can apply to achieve the Motor Target. Larger values will cause the motor to be stronger.
Correction Time
Specifies how gradually the constraint attempts to correct deviations from the Motor Target.
Constraint Force Mixing
Increasing this value makes the motor component of the constraint softer. A small positive value can increase the stability of the simulation.
Target Angular Stiffness
Specifies the strength of the force that attempts to match the motor target orientation.
This value is equivalent to the frequency of a spring.
Target Angular Damping Ratio
Specifies how much damping is applied to the motion when matching the motor target orientation. A value of 0 specifies no damping, and a value of 1 provides just enough damping to prevent oscillation. Values between 0 and 1 allow oscillation (with some damping), and values greater than 1 provide increasingly damped motion that has no oscillation.
This value is equivalent to the damping ratio of a spring.
Target Position Stiffness
Specifies the strength of the force that attempts to match the motor target position.
This value is equivalent to the frequency of a spring.
Target Position Damping Ratio
Specifies how much damping is applied to the motion when matching the motor target position. A value of 0 specifies no damping, and a value of 1 provides just enough damping to prevent oscillation. Values between 0 and 1 allow oscillation (with some damping), and values greater than 1 provide increasingly damped motion that has no oscillation.
This value is equivalent to the damping ratio of a spring.
Constraint Iterations
If greater than zero, overrides the number of iterations performed by
the constraint solver for this constraint. If some groups of
constraints require more iterations than others, this parameter can be
used instead of globally increasing the number of iterations on the
solver.
Disable Collisions
Disables collision detection between the constrained pair of objects.
Guide Options ¶
Show Softness Threshold
Show where the constraint begins to take effect. This is only used if Softness is greater than 0 and less than 1.
Color
The color of the primary guide geometry.
Secondary Color
The color of the secondary guide geometry. This includes the Softness Threshold and the indicator of the current twist.
Guide Size
Scales the guide geometry.
Show Object Link
This parameter controls the display of guide geometry connecting the constraint to the constrained object.
Parameter Operations
Each data option parameter has an associated menu which specifies how that parameter operates.
Use Default
Use the value from the Default Operation menu.
Set Initial
Set the value of this parameter only when this data is created. On all subsequent timesteps, the value of this parameter is not altered. This is useful for setting up initial conditions like position and velocity.
Set Always
Always set the value of this parameter. This is useful when specific keyframed values are required over time. This could be used to keyframe the position of an object over time, or to cause the geometry from a SOP to be refetched at each timestep if the geometry is deforming.
You can also use this setting in
conjunction with the local variables for a parameter value to
modify a value over time. For example, in the X Position, an
expression like $tx + 0.1 would cause the object to
move 0.1 units to the right on each timestep.
Set Never
Do not ever set the value of this parameter. This option is most useful when using this node to modify an existing piece of data connected through the first input.
For example, an 
RBD State
DOP may want to animate just the mass of an
object, and nothing else. The Set Never option could be used
on all parameters except for Mass, which would use Set
Always.
Default Operation
For any parameters with their Operation menu set to Use Default, this parameter controls what operation is used.
This parameter has the same menu options and meanings as the Parameter Operations menus, but without the Use Default choice.
Data Sharing
Controls the way in which the data created by this node is shared among multiple objects in the simulation.
Data sharing can greatly reduce the memory footprint of a simulation, but at the expense of requiring all objects to have exactly the same data associated with them.
Share Data Across All Time
This node only creates a single piece of data for the whole simulation. This data is created the first time it is needed, so any expressions will be evaluated only for the first object.
All subsequent objects will have the data attached with the same values that were calculated from the expressions for the first object. It is important to note that expressions are not stored with the data, so they cannot be evaluated after the data is created.
Expressions are evaluated by the DOP node before
creating the data. Expressions involving time will also only be
evaluated when this single piece of data is created. This option
is appropriate for data that does not change over time, and is
the same for all objects, such as a 
Gravity
DOP.
Share Data In One Timestep
A new piece of data is created for each timestep in the simulation. Within a timestep though, all objects have the same data attached to them. So expressions involving time will cause this data to animate over time, but expressions involving the object will only evaluate for the first object to which the data is attached.
This option is appropriate for data that changes
over time, but is the same for all objects such as a 
Fan Force
DOP, where the fan may move or rotate over time.
Activation
Determines if this node should do anything on a given timestep and for a particular object. If this parameter is an expression, it is evaluated for each object (even if data sharing is turned on).
If it evaluates to a non-zero value, then the data is attached to that object. If it evaluates to zero, no data is attached, and data previously attached by this node is removed.
Group
When an object connector is attached to the first input of this node, this parameter can be used to choose a subset of those objects to be affected by this node.
Data Name
Indicates the name that should be used to attach the data to an object or other piece of data. If the Data Name contains a “/” (or several), that indicates traversing inside subdata.
For example, if the Fan Force DOP has the default Data Name
“Forces/Fan”. This attaches the data with the name “Fan” to an
existing piece of data named “Forces”. If no data named “Forces”
exists, a simple piece of container data is created to hold the
“Fan” subdata.
Different pieces of data have different requirements on what names should be used for them. Except in very rare situations, the default value should be used. Some exceptions are described with particular pieces of data or with solvers that make use of some particular type of data.
Unique Data Name
Turning on this parameter modifies the Data Name parameter value to ensure that the data created by this node is attached with a unique name so it will not overwrite any existing data.
With this parameter turned off, attaching two pieces of data with the same name will cause the second one to replace the first. There are situations where each type of behavior is desirable.
If an object
needs to have several Fan Forces blowing on it, it is
much easier to use the Unique Data Name feature to ensure that
each fan does not overwrite a previous fan rather than trying to
change the Data Name of each fan individually to avoid
conflicts.
On the other hand, if an object is known to have RBD
State data already attached to it, leaving this
option turned off will allow some new RBD State
data to overwrite the existing data.
Inputs ¶
First Input
This optional input can be used to control which simulation objects are modified by this node. Any objects connected through this input and which match the Group parameter field will be modified.
If this input is not connected, this node can be used in conjunction with an Apply Data node, or can be used as an input to another data node.
All Other Inputs
If this node has more input connectors, other data nodes can be attached to act as modifiers for the data created by this node.
The specific types of subdata that are meaningful vary from node to
node. Click 
an input connector to see a list of available
data nodes that can be meaningfully attached.
Outputs ¶
First Output
The operation of this output depends on what inputs are connected to this node. If an object stream is input to this node, the output is also an object stream containing the same objects as the input (but with the data from this node attached).
If no object stream is
connected to this node, the output is a data output. This data
output can be connected to an 
Apply Data DOP,
or connected directly to a data input of another data node, to
attach the data from this node to an object or another piece of
data.
Locals ¶
channelname
This DOP node defines a local variable for each channel and parameter on the Data Options page, with the same name as the channel. So for example, the node may have channels for Position (positionx, positiony, positionz) and a parameter for an object name (objectname).
Then there will also be local variables with the names positionx, positiony, positionz, and objectname. These variables will evaluate to the previous value for that parameter.
This previous value is always stored as part of the data attached to the object being processed. This is essentially a shortcut for a dopfield expression like:
dopfield($DOPNET, $OBJID, dataName, "Options", 0, channelname)
If the data does not already exist, then a value of zero or an empty string will be returned.
DATACT
This value is the simulation time (see variable ST) at which the current data was created. This value may not be the same as the current simulation time if this node is modifying existing data, rather than creating new data.
DATACF
This value is the simulation frame (see variable SF) at which the current data was created. This value may not be the same as the current simulation frame if this node is modifying existing data, rather than creating new data.
RELNAME
This value will be set only when data is being attached to a relationship (such as when Constraint Anchor DOP is connected to the second, third, of fourth inputs of a Constraint DOP).
In this case, this value is set to the name of the relationship to which the data is being attached.
RELOBJIDS
This value will be set only when data is being attached to a relationship (such as when Constraint Anchor DOP is connected to the second, third, of fourth inputs of a Constraint DOP).
In this case, this value is set to a string that is a space separated list of the object identifiers for all the Affected Objects of the relationship to which the data is being attached.
RELOBJNAMES
This value will be set only when data is being attached to a relationship (such as when Constraint Anchor DOP is connected to the second, third, of fourth inputs of a Constraint DOP).
In this case, this value is set to a string that is a space separated list of the names of all the Affected Objects of the relationship to which the data is being attached.
RELAFFOBJIDS
This value will be set only when data is being attached to a relationship (such as when Constraint Anchor DOP is connected to the second, third, of fourth inputs of a Constraint DOP).
In this case, this value is set to a string that is a space separated list of the object identifiers for all the Affector Objects of the relationship to which the data is being attached.
RELAFFOBJNAMES
This value will be set only when data is being attached to a relationship (such as when Constraint Anchor DOP is connected to the second, third, of fourth inputs of a Constraint DOP).
In this case, this value is set to a string that is a space separated list of the names of all the Affector Objects of the relationship to which the data is being attached.
ST
The simulation time for which the node is being evaluated.
Depending on the settings of the 
DOP Network
Offset Time and Scale Time parameters,
this value may not be equal to the current Houdini time
represented by the variable T.
ST is guaranteed to have a value of zero at the
start of a simulation, so when testing for the first timestep of a
simulation, it is best to use a test like $ST == 0, rather than
$T == 0 or $FF == 1.
SF
The simulation frame (or more accurately, the simulation time step number) for which the node is being evaluated.
Depending on the settings of the DOP Network parameters,
this value may not be equal to the current Houdini frame number
represented by the variable F. Instead, it is equal to
the simulation time (ST) divided by the simulation timestep size
(TIMESTEP).
TIMESTEP
The size of a simulation timestep. This value is useful for scaling values that are expressed in units per second, but are applied on each timestep.
SFPS
The inverse of the TIMESTEP value. It is the number of timesteps per second of simulation time.
SNOBJ
The number of objects in the simulation. For nodes that
create objects such as the 
Empty Object DOP,
SNOBJ increases for each object that is evaluated.
A good way to guarantee unique object names is to use an expression
like object_$SNOBJ.
NOBJ
The number of objects that are evaluated by the current node during this timestep. This value is often different from SNOBJ, as many nodes do not process all the objects in a simulation.
NOBJ may return 0 if the node does not
process each object sequentially (such as the 
Group
DOP).
OBJ
The index of the specific object being processed by the node. This value always runs from zero to NOBJ-1 in a given timestep. It does not identify the current object within the simulation like OBJID or OBJNAME; it only identifies the object’s position in the current order of processing.
This value is useful for generating a
random number for each object, or simply splitting the objects into
two or more groups to be processed in different ways. This value
is -1 if the node does not process objects sequentially (such
as the Group DOP).
OBJID
The unique identifier for the object being processed. Every object is assigned an integer value that is unique among all objects in the simulation for all time. Even if an object is deleted, its identifier is never reused. This is very useful in situations where each object needs to be treated differently, for example, to produce a unique random number for each object.
This value is also the best way to look up information on an object using the dopfield expression function.
OBJID is -1 if the node does not process objects
sequentially (such as the Group DOP).
ALLOBJIDS
This string contains a space-separated list of the unique object identifiers for every object being processed by the current node.
ALLOBJNAMES
This string contains a space-separated list of the names of every object being processed by the current node.
OBJCT
The simulation time (see variable ST) at which the current object was created.
To check if an object was created
on the current timestep, the expression $ST == $OBJCT should
always be used.
This value is zero if the node does not process
objects sequentially (such as the Group DOP).
OBJCF
The simulation frame (see variable SF) at which the current object was created. It is equivalent to using the dopsttoframe expression on the OBJCT variable.
This value is zero if the node does not process objects
sequentially (such as the Group DOP).
OBJNAME
A string value containing the name of the object being processed.
Object names are not guaranteed to be unique within a simulation. However, if you name your objects carefully so that they are unique, the object name can be a much easier way to identify an object than the unique object identifier, OBJID.
The object name can
also be used to treat a number of similar objects (with the same
name) as a virtual group. If there are 20 objects named “myobject”,
specifying strcmp($OBJNAME, "myobject") == 0 in the activation field
of a DOP will cause that DOP to operate on only those 20 objects.
This value is the empty string if the node does not process objects
sequentially (such as the Group DOP).
DOPNET
A string value containing the full path of the current DOP network. This value is most useful in DOP subnet digital assets where you want to know the path to the DOP network that contains the node.
Note
Most dynamics nodes have local variables with the same names as the
node’s parameters. For example, in a 
Position DOP,
you could write the expression:
$tx + 0.1
…to make the object move 0.1 units along the X axis at each timestep.
| See also |
Slider Constraint Relationship
Spring Constraint Relationship
