-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I found a bug #1
Comments
As per the documentation, the destinationMesh flag declares the mesh that will be re-ordered. In the snippet that you posted, that means that pCube1 will be re-ordered to "match" pCube2, based on the topology map determined by the declared components. Given the names, it looks like you were using default cubes. In that case, your selections are not topologically congruent. I've attached a screen shot that shows the components you declared. See how they are not "the same" components on the mesh? The re-order command will accept any source components pairs, but it won't create the "same" mesh unless the source components are the "same". Does that make sense? I hope this helps. |
emmmm, you not understood my meaning, so, I want to re-order them vertex order. I use polyReorder yes, B polycube vertex order transfer to A, successful! But, if I apply A to B, I want to be got the result is B polycube vertex order by A vertex order transfer to, I read the documentation, the flag rule I understand. |
Ok. I understand now. Please provide a Maya scene with the two cubes you describe so that I may debug this issue. I'm on vacation for the rest of the year so I won't have a chance to look into this until January. If you want to try to debug it yourself, I would welcome a merge request. |
if I reorder A to B,
like it
cmds.polyReorder(dm='pCube1',dc=['pCube1.vtx[3]','pCube1.e[7]','pCube1.f[1]'],sm='pCube2',sc=['pCube2.vtx[2]','pCube2.e[6]','pCube2.f[5]'])
B normal changed, but B vertexID not change
if I exchange both
dm to sm , sm to dm
everything is successful.
why?
The text was updated successfully, but these errors were encountered: