Hey, I did a build from example quadruped rig and IK->FK switch doesn’t work. It works for Biped template though.
“mgear\core\anim_utils.py line 210: No object matches name: frontLegUI_L0_ctl.leg_L0_ctl //”
Adding to this question:
- How did you get that popup menu to show up? Holding right-click brings up the standard Maya menu for me.
- Building the standard quad template, I don’t see anything in the synoptic view for switching IK/FK or spaces (though I see everything in the biped template). Is it possible to do this kind of switching with the leg_3jnt_01 component? I’m currently on mGear 3.1.1 on a Mac.
(I am loving this system btw 
)
Thanks for the response! You say it’s possible… does the quadruped template just not have it in the current version (meaning I have to add it myself), or should it already be there when I build? I’m just trying to figure out if its absence is a bug or not. Thanks!
Hey, I’m not sure about previous versions how it was with quadruped template, I didn’t have to use it before.
But this code is working fine for toggle between IK and FK on 3jnt leg, I checked it:
Hello guys
As an overall note I will say that the RightClick menu switching/snap capabilitties is probably not compatible with all things in mGear. With @Miquel we know that there are some inconsistencies between the right click menu, synoptic and other things but we will probably get to a point in time where this will dissolve the further we keep developing. Synoptic allows you to setup what are the matching controls on a switch whether the right click menu trying to generalize rules for this but not all components are ready for this or have been tested .
@Miquel is about to do an update that already bring some fixes to the right click menu and other exiting things 
Stay tuned.
Cheers
3 Likes
I was having the same problem and I discovered the guide grp was the problem.
1- I make a new guide group by creating a new control_01 and then delete the control_CO_root node.
2-Copy the global_Co_root(and its children from under the orig guide node)to new guide node(which will be called guide1 )
Then rebuild the rig and the right click FKIK matching works
we have ready a big improvement in the FKIK matching functionality and Rightclick menu
here is the main ticket that fixed the related issues https://github.com/mgear-dev/mgear_core/issues/62
I will explain the changes in the next mGear dev log on the youtube channel
1 Like
Fantastic. Thanks for your hard work.
Edit: Nevermind! On a fresh release, and grabbing your latest 2 files, it works. So it’s something I changed in my own branch.
I grabbed your latest dagmenu.py and anim_utils.py and I’m getting an error when trying to space switch with the dagmenu.
// Error: TypeError: file /production/mGear/tools/mgear_3.6.0/release/scripts/mgear/core/dagmenu.py line 272: 'NoneType' object is not iterable //
This happens on IK/FK switching and switching space on custom controls. (It was happening on IK/FK switching before for me too. So I’m investigating now.)
Was there anything else I need to grab from the code to take advantage of this fix? I saw you mentioning naming the attributes based on name instead of type. So maybe you changed some code in the shifter modules?
(I’m working on an answer too.)
The rigs have new attr and message connections. You can’t use it without rebuild the rig with the latest shifter, sorry 
That was needed in order to support the new naming rule system
I get it. But I didn’t see any of those files in the commit. Is there a way I can see what files changed?
Is it just the shifter module I also need?
yes, the commits are in shifter
Which repos should I get latest to use the shifter dagMenu fix on the FKIK matching? I’m on 3.6.5.
I grabbed latest:
mgear-dev/shifter
mgear-dev/mgear_core
& updated the guide in my scene but getting error:
# Warning: Unrecognized node type 'mgear_matrixConstraint'; preserving node information during this session. #
# Error: RuntimeError: file /Applications/Autodesk/maya2018/Maya.app/Contents/Frameworks/Python.framework/Versions/Current/lib/python2.7/site-packages/pymel/core/general.py line 221: The destination attribute 'unknown1.driverMatrix' cannot be found. #
we have a new custom solver to simplify the graph, I am polishing it this week. it is working nicely, But it is not ready to use yet since I want to add some changes.
in order to work around it. You can force to use the old method, setting Vanilla_nodes = True
in the components/init.py line 229
Should be ready tomorrow or the day after.
EDIT: here is the compiled solver for OSX in Maya 2020 https://we.tl/t-tTfBWPdOd7
Don’t use it for production. But at less you can try
2 Likes
@Count_zer0 Maya 2020 OSX solver update with the final plug names https://we.tl/t-Fz87L8Ti74
the latest shifter and mgear_core commits are needed to use this solvers.
I will be posting a mGear 3.7 Beta next week
2 Likes