M6's new mesh constraint with isSoft = crash?

[campbell]

hey,

seem to be getting a repeatable crash from attempts to do local solves on cloth that have an 'isSoft' Mesh constraint applied to them. running local sims on these die straight away and the same type of symptoms mentioned in the release notes regarding cloth and changing the collision offset/depth of Mesh constrain targets occur: that is, loss of hotkeys/MMs, and in mycase, upon closing maya some form of memory exception related to these interface items occurs (win2k). the remedies in those notes failed to resolve this problem. i was unable to reproduce these same symptoms by way of the documented problem, only by flipping the isSoft attribute on.

local sims when using cloth Transform constraints that are set to isSoft do not break.

In reply to:
// build signle panel cloth object, a collision object, and
// a Mesh constraint to that collision object which is
// set to isSoft

nurbsSquarePreset(0,0,0,0,0,1,0,1,1,1,3,1);
nurbsSquare -c 0 0 0 -nr 0 1 0 -sl1 1 -sl2 1 -sps 1 -d 3 -ch 1 ; objectMoveCommand;
scale -r 22.436277 22.436277 22.436277 ;
performCloth createGarment;
polyCube -w 1 -h 1 -d 1 -sx 3 -sy 3 -sz 3 -ax 0 1 0 -tx 1 -ch 1;
scale -r 3.634462 3.634462 3.634462 ;
move -r -os -wd 0 4.005965 0 ;
move -r -os -wd 0 0 8.058585 ;
performCloth createCollisionObject;
select -r cloth1.vtx[1:4] cloth1.vtx[22:23] cloth1.vtx[27] cloth1.vtx[35:36] ;
select -tgl pCube1 ;
performCloth createMeshConstraint;
setAttr "meshConstraintShape1.isSoft" 1;

On the same note of 'soft' cloth constraints, it would seem that setting initial cloth state fail to cache the constraint spring states? when you go to do either a scene-time cache or a local sim seeded from a stored inital state you get an immediate sag out from the soft constraint, as if the springs hadn't settled yet and are pushing out to (a displaced) rest state again ..

any and all thoughts or experiences appreciated!
cheers.