Hi Yukio I have not heard of the pnts attribute before nor has it crossed my slow ongoing review of the api documentation, but now that you've pointed me in the right direction I feel like I should have known about pnts years ago... :)
Thanks for your help Chad On Sep 11, 2013 5:59 AM, <[email protected]> wrote: > you can store the mesh difference in the pnts attribute of a mesh node or > vlist of a tweak node. > > pseudo code: > loop over verts: > tweak = deformVertPosition - orignalVertPosition > setAttr('msh.pnts[vert]', tweak.x, tweak.y, tweak.z) > > > Quoting Chad Fox <[email protected]>: > > Hi all, >> >> Despite my best efforts on reading up on how to view and or edit vertex >> tweak data, the api documentation on it is a little out of my league right >> now. I would like to solve this one problem in the mean time and I could >> use your help. >> >> I've been testing outMesh to inMesh connections with three heads (all >> modelled from the same base head/topology) a base head (neutral), the same >> head with puffed cheeks, and one _new_ re-portioned base head. My goal >> here >> is to plug the reproportionedHead.outMesh into the puffedCheeks.inMesh >> resulting in the puffedCheeks head inheriting the new head proportions >> while keeping the puffed cheeks. >> >> I have found this works as planned if I model the original puffed cheeks >> using xform tools (translate, rotate and scale) only. As I understand it >> the resulting changes are stored as 'tweaks' in the shapenode. >> >> Now to the problem: I have face shapes like puffedCheeks that were >> modelled >> using deformers or imported from zbrush, etc. Unfortunately these don't >> contain the important tweak data so I lose the puffed cheeks or other face >> shape when a new re-proportioned head mesh is plugged into these shape's >> inMesh attribute. >> >> Is it possible to take an object like puffedCheeks, which does not have >> tweaks, and compare it to a base head then store the difference/tweak data >> into the puffedCheeks shape? >> >> In case my written explaination was not 100% clear I've created an >> animated >> gif of the examples in action. Follow the link to view: >> https://docs.google.com/file/**d/0B-**i5vZUcAFTgdTViaE9BbUwtOEU/** >> edit?usp=sharing<https://docs.google.com/file/d/0B-i5vZUcAFTgdTViaE9BbUwtOEU/edit?usp=sharing> >> >> Thanks for your time, >> >> Cheers >> >> -Chad Fox >> www.chad-fox.com >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Python Programming for Autodesk Maya" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to >> python_inside_maya+**[email protected]<python_inside_maya%[email protected]> >> . >> To post to this group, send email to python_inside_maya@** >> googlegroups.com <[email protected]>. >> For more options, visit >> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >> . >> >> > > > ------------------------------**--------- > Yukio Satoh > VFX Artist // TD > > www.satoh.ch > www.elefantstudios.ch > ------------------------------**--------- > > -- > You received this message because you are subscribed to the Google Groups > "Python Programming for Autodesk Maya" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to > python_inside_maya+**[email protected]<python_inside_maya%[email protected]> > . > To post to this group, send email to > python_inside_maya@**googlegroups.com<[email protected]> > . > For more options, visit > https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> > . > -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
