Deformer delema

Semicharm

There's a few issues with deformers (aka magnets) I'm trying to solve. First, I can't get DS set a new "default" value for a deformer channel from a Poser pose file. The following works in Poser, but DS refuses to obey "initValue". It works in correctly in about everything else, just not deformerPropChan.

actor chest
{
 channels
 {
  deformerPropChan BrstLift_rChest_Dfmr:1
  {
   initValue 0.375
   keys
   {
    k 0  0.375
   }
  }
 }
}

Second, I can't figure out how to apply the above to clothing in Poser. Using a "magnetize" pose on clothing gets Poser to apply the magnets, but that creates a new set of deformer channels on the clothing which do not conform to the figure's channels. Changing the deformer value on the figure has no effect on the clothing. (The "include morphs" setting doesn't do it either.) That wouldn't be to much of a problem if I could set them from a pose file, but the above doesn't work. I tried changing or removing the figure number (the ":1" at the end of the channel name) but no dice.

Any suggestions or workarounds?

Semicharm

Good news and bad news on the Poser issue. Good news is that I found out there's a special "conformParm" value that can be added to a channel to make it conforming. It works on deformerPropChan too!

Bad news is that it doesn't work in anything before Poser 9. Also, I don't think there's any UI option for setting this. It seems that it can only be set using the WantsConform() Parameter method in Python or by manually editing the Poser file to add the conformParm values.

Semicharm

Finally got the pose file to work in Poser. I deleted the clothes, reloaded it, conformed it, applied the figure's magnet pose, then applied my fix pose. Not sure what I did differently but at least it works. This isn't the first time I had issues with setting deformer channel values in Poser though.

Also found a "fix" for the DS issue.

actor chest
{
 channels
 {
  deformerPropChan BrstLift_rChest_Dfmr:1
  {
   initValue 0.375
   forceLimits 4
   min 0.375
   max 0.375
   keys
   {
    k 0  0.375
   }
  }
 }
}

It's not an elegant solution, but at least it pins down the compatibility use.