Hi,

Linux H8.1.655

I think I might have found a typo inside the WireGlueGroupConstraint DOP.

This is actually an OTL, which contains an “Anchor: World Space Rotation” DOP called: anchorworldspacerot2

That inner DOP is using the Data Name: “Anchor” when i think it should be using: “GoalAnchor”. (?)

cheers,
ben.

ben simons
That inner DOP is using the Data Name: “Anchor” when i think it should be using: “GoalAnchor”. (?)

“GoalAnchor” would be consistent with the other anchors. However, this should not be a problem as the name of anchors do not affect the constraint's behaviour. The first anchor always refers to the current object and the second anchor refers to the goal object.

All anchor will have consistent naming in Houdini 9.

Thanks Derrick!

I was actually changing this DOP to one which uses two Anchor Point Number
Position DOP's when I noticed the inconsistency. So - the data names are
just what then appears in the Details view, and that's all? I'm just trying to
better understand how it works at this level.

I'd wondered if this different name was something to do with needing a
unique dataname, or a mod on goal ordering (for rotation order?),
or … unimportant!

From what you've said, I gather that the Constraint DOP uses the internal
dataTypes, like “SIM_ConAnchorWorlsSpaceRot” to work out what is a valid
anchor?

I'm not sure what determines which is the “first” anchor. Is it the way a
constraint DOP is wired (counting inputs, from left to right)? The details
view lists the anchors and con-relat's in what appears to be unsorted order.
eg. I see:

ConstraintRot_3
- Anchor
- ConRelHard
- WireAnchor
Constraint_3
- ConRelHard
- GoalAnchor
- WireAnchor