Loading...
> >

Applied Puppeteer pose not same as that saved

stitlownstitlown Posts: 294
in Daz Studio Discussion

Before I post a bug for this, I thought I'd see if anyone else has seen the same issue.

I have one pose in a quite extensive puppeteer set for G2M where the -r and -l shoulder bone rotations are nothing like the saved pose rotations. Only this bone (althought the poses are pretty much zero for all the trunk and lower limb bones) - not the collars and not any of the child bones - including some quite intricate hand poses. Is not affecting my G2F characters in the same scene.

There are some broadly similar poses (hands cupped in front of the chest) where this problem does not arise in the same scene / puppeteer layer. The corrected pose can be copy / pasted successfully from one figure to another, but for all the G2M (well I only tried on 2 of 5) the puppeteer pose produces the same wierd different shoulder rotations.

Any one else seen this??? Any thoughts??? Maybe some seriously problematic IK issue that can be reset??? with a <zero pose> and manual re-pose???

Cheers, Lx

Comments

  • takezo_3001takezo_3001 Posts: 1,997
    edited July 2021

    I don't know if this contributes to the issue you're having, but are your poses done with the limits turned off by chance? It may be re-setting the poses with limits on, I don't know for sure as I never pose my characters with limits turned off... I haven't seen this issue as much, but I have had the poses, not in the 100% original pose, I hope they get this fixed as I use puppeteer extensively!

    Post edited by takezo_3001 on
  • stitlownstitlown Posts: 294

    Thanks for the tip,@takezo_3001. I was aware of the "limits" issue and limits are in use, both for the posing and the puppeteering.  Since posting, I've done some other poses built from the problem one, and they work fine (minor head movements, visemes and expressons, and only minor limb or digit movements). And those successful pose captures were in the same daz session as the problem one.

    So must just be some wierd bizzaro glitch when certain values in combination are "just so". Not worth raising a bug report for. If I was obsessive, I could probably jump into the .duf and manually edit a correction.

    Cheers, Lx

Sign In or Register to comment.