Cameron White


About Me



Recent Forum Posts

Simulate crowd, not so easy June 27, 2017, 10:06 a.m.

I think that option was replaced by Ctrl+clicking to build a default setup, since it previously was very easy to accidentally create that when you thought that some agents were selected

Constraint Networks - aargh June 23, 2017, 4:42 p.m.

The issue is the expression for the Object Merge SOP inside the apply_force_to_disconnected SOP solver. Using
stamps("..", "DATAPATH", ...)
isn't correct since you're in a SOP solver running over DOP objects, and so the object merge gives you the current DOP object's geometry instead when the sop solver cooks. In this case, you want to read from a specific constraint network's geometry, and so you can just use the last section of the stamps() expression (see attached file)

Constraint Networks - aargh June 12, 2017, 10:52 a.m.

The anchor points on the constraint network are attached to objects based on their ‘name’ point attribute, which can specify either the name of a DOP object, the name of a packed primitive (using its ‘name’ point attribute), or a combination of the two ('dop_object_name/packed_prim_name') to avoid ambiguous references. The constraint network help card [] has some more details on this.

Your setup was very close to working - I added one node to name the pieces, and then switched the constraint setup to use those points as the input so that the name attribute was carried over to the constraint network's anchor points.