Home Website Youtube GitHub

Trying to update a rig built with an older version of mGear

Support
#1

Hello!
I wanted to use euGear for a project but the rig I’m using is built with an older version of mGear. From what I saw, euGear 1.0 (I need the control rig in UE) only works with rigs created in mGear5.0 onwards, so I tried to update my old rig with the update function.
After that, however, every time I try to open the settings of the guide to enable “Collect data on external drive”, it prompts me the following error:
MayaAttributeError: file C:\Users…\Documents\maya\modules\scripts\mgear\pymaya\node.py line 450: No ‘joint_worldOri’ attr found

If I try to rebuild the rig from the guide, it doesn’t build the same as before, maybe I’m doing something wrong?
I’m not even sure if the guide updated properly to the newer version since all that seems to happen is it creates an empty group called ‘guide’. Any ideas what the issue might be?

#2

the update guide function should hace added that joint_worldOri attr.
Can you try again?
Just to be sure, is the same update command mention here: Backward compatibility issue - #3 by Gabriel
Right?

#3

Yes, I’m using the same ‘Update Guide’ command, but then I get this error:

The guide doesn't seem to be up to date.Check logged messages and update the guide.
Guide loaded from hierarchy in  [ 0:00:01.967562 ]
# Error: RuntimeError: file C:\Users\...\Documents\maya\modules\scripts\mgear\pymaya\cmd.py line 266: Error occurred while calling wrapped function 'maya.cmds.parent': No object matches name: guide_old|controllers_org
# Arguments: ('guide_old|controllers_org', '|guide')
# Keyword Arguments: {}
# Command for debugging: maya.cmds.parent('guide_old|controllers_org', '|guide', )

As well as a wall of those:

Can’t find parameter ‘rig_name’ in |guide_old
Can’t find parameter ‘mode’ in |guide_old
Can’t find parameter ‘step’ in |guide_old
Can’t find parameter ‘ismodel’ in |guide_old
…

I’m not the one that created the original rig so I am not sure what all this means and if the creator has done something additional. Let me know if I should send more from the log. Thanks!

#4

How old is the original rig?

There have been times for me when the update function wasn’t able to jump too many versions at once. And I had to load a middle version of mGear, and update in 2 stages.

I don’t have any info about which versions are compatible. But if your rig is very old you might have to try something similar.

It might also be possible to export as a template in the older version of mGear, and load it as a template in the newer version, rather than updating. But there might be version limits for that too.

#5

Do you have more than one guide in the scene?
This not should affect, but is a scenario that I didn’t test

#6

No, I have only one guide in the scene.
I can’t find the version the old rig was built with but I can try updating it with older versions of mGear. I will also test exporting it as a template as suggested.
If not, I think I’ll just redo the rig in 5.1.
Thanks a lot!

#7

If you have the scene in .ma, you can open it in a text editor and search for “gear_version”. Or in Maya you can check that attribute on the top rig transform. (And maybe the guide root too.)

setAttr -k on ".gear_version" -type "string" "4.0.9";