Solver UI - Incorrect object gets added to solver in v0.3.8 #165
Comments
|
Hello Etienne, This is obviously a bug, and was meant to be fixed by #153. Is it possible to send me a scene file that reproduces the problem? If I don't have any scene file, I can still attempt to fix the problem blindly but I have not way of testing myself. David |
|
Hello David, I considered including the scene files, but the rig is running
on prioritary plugins only compiled for our os at rodeo.
I'll try and reproduce the hell issue without any fancy rigs loaded in!
…On Thu., Oct. 22, 2020, 7:56 p.m. David Cattermole, < ***@***.***> wrote:
Hello Etienne,
This is obviously a bug, and was meant to be fixed by #153
<#153>.
I'm not sure what's causing it (yet), but I will investigate and I will
release a v0.3.9 as soon as I can.
Is it possible to send me a scene file that reproduces the problem?
I don't need models at all, just the outer rig controls - only enough to
reproduce the problem.
If I don't have any scene file, I can still attempt to fix the problem
blindly but I have not way of testing myself.
I could produce a new pre-release of v0.3.9 with my changes for Maya 2018
on (CentOS) Linux, then you can test and let me know?
David
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#165 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARPIBHVL4ZLXUVXC2PC2I4DSMDBBDANCNFSM4S3UZPHA>
.
|
|
I have a possible solution to this problem, and it will be released in v0.3.9 (soon). Once it's released, please let me know if the problem is fixed or not. David |
|
My pleasure David, We will install 0.3.9 as soon as possible and see if the issue is resolved. |
|
@RodeoPerchaude can you confirm if this is working for you? Or maybe try v0.3.10? |
|
I know a lot more information about this bug now! It seems the problem is caused by duplicate UUIDs on the nodes. By default each node in Maya will have different UUID values. However, if you create a scene file with a UUID, A lot of mmSolver assumes that two nodes can always be fetched with the UUID, and there is only one node with the same UUID. David |
david-cattermole
changed the title
|
Thanks a lot for the detective work David and Patcha. |
Issue #165. Uses the already existing MPlug and converts this directly to a node path. Unlike the name UUID suggests, there are cases when multiple nodes in the Maya scene have the same UUID.
Fixes issue #165. The most common occurrence is when the same rig is referenced into the Maya scene more than once AND the rig was saved in Maya 2016+. When saving in a Maya version that contains the UUID feature (introduced in Maya 2016) the UUIDs are saved into the referenced file. The UUIDs are then read from the referenced file and having the same scene file loaded into Maya will cause duplicate UUIDs to exist.
|
Hello @RodeoPerchaude, I have researched this bug and I've implemented a fix which will be ready in v0.3.11 (hopefully out this weekend). Just to be clear, forcing the rig to have unique UUIDs will not stop this problem happening 100%. If you load the rig file My fix will stop the duplicate UUIDs for Attributes in the Solver from causing weirdness. David |
Hello all, following a conversation with Patcha, I am creating a"ticket" on the board.
Let me know if I am doing it wrong, and thanks for looking into it eventually.
Aside from this issue, 0.38 has been really stable for me so far.
14-20 hours without issues.
Problem / Feature
When selecting an object and adding it to the solver output attributes, another unrelated object gets added in it's place.
Exemple:
selecting: characterBucky_001:R_arm_1_FK_CON
added to the solver: characterBucky_001:R_foot_IK_CON
Steps to Reproduce
Software Versions
Maya 2018.6
mmSolver version:
0.38
Maya version:
Maya 2018.6
Operating System (OS): Rodeo's centOs
The text was updated successfully, but these errors were encountered: