Well Im happy to have at least found a solution that is working, will call
this done for now, unless anyone has another idea.
The last idea you had of iterating over it multiple times seems fine to me.
So long as it doesn’t bother you performance wise, it is very robust. I
would probably do someth
Cool, I'll definitely check it out.
The thing about this that makes it tricky, is that all of the positions are
generated. This tool lets you mirror a pose around an arbitrary plane, so
the driving factors are the world space points. So sadly there is no ground
truth to begin with. On top of that,
For more elegance, have you considered storing the local matrix, instead of
the world? Or better yet, store the translate/rotate values? Is it not safe
to assume that wherever you export these from will have a similar - if not
identical - hierarchy?
@marcus, you will have to share your secret :)
My code formatting didnt quite work, @marcus, you will have to share your
secret :)
On Monday, February 15, 2021 at 3:31:20 PM UTC+1 Eric Bates wrote:
> Thanks so much Marcus for the really thoughtful and complete reply!
>
> I managed to get it working through a combination of approaches.
>
> I
you can get rid of all the matrix part by setting directly the matrix in
world space, using
cmds.xform(obj, matrix=your_mat, worldSpace=True)
Le lundi 15 février 2021 à 02:42:49 UTC-5, Marcus Ottosson a écrit :
> If I understand you correctly:
>
>1. You’ve got a dictionary of worldMatrices
If I understand you correctly:
1. You’ve got a dictionary of worldMatrices associated to names of
controls
2. They are unordered, e.g. could be pinky and then shoulder.
3. You’d like these assigned to their associated control
If so, then what you’re looking for isn’t evaluation order
