Testing out mgear. 3.2.0. What an amazing tool!
I seem to have an issue with the leg_3jnt_01 adding world_ctl to the upVref constraint array upon build without me asking it to. Wouldn’t be a big deal, but it messes up the order that the condition nodes plug into the upV_constraint, making the enum attribute entries for upVref switching have an offset, and not being able to switch to the last array entry. See attached image.
I’ve tried the base quadruped template, and a more basic shifter rig with just less components. I also tried mgear 3.1.1 and 2.6.1 and seem to get the same problem.
Anyone else getting this issue, or have I missed something? If it’s a bug, I’ll probably set up a post-build step to remap the condition plugs going into the constraint, ignoring the world_ctl.