Hey Guys,
Just trying to get 3.2 working on mac. I’ve installed it correctly as per video.
It seems to be able to build simple arms joints properly, but when i select the biped template it gets stuck building it at the spine joint.
Attaheched a few images for refernece. Any help would be appreaciated.
Using maya 2019, mgear 3.2.0
thanks,
tom
Is it a fresh biped template, or did you make any changes at all?
Do you have only one guide in the scene? If you have more than one guide, I would suspect a possible name clash.
Can you see if it is this bug, where sometimes guides get named with a double L0_L0 or R0_R0 or C0_C0?
Also, for error messages, it’s better just to paste the text, instead of a screenshot of the text. It makes it easier to copy/paste stuff and go searching into files.
Also, what do you have selected when you build? You should select the “guide” node at the top, right?
EDIT: ALSO, I don’t think the MacOS solvers have been officially released for Maya 2019 yet.
They can be downloaded here, but I don’t think they are in the release yet. Spider-Verse mGear Rig, and Mac Installation
Did you install those solvers? I’m not sure if that would cause or fix the errors you’re seeing, but you’ll need those.
Hey Chris,
Thanks for helping me out with this. Yeah its a fresh template, no changes made.
I just go mGear > Shifter > Guide template samples > Biped on a new scene and i get the error.
I suspect those solvers might the case, It might sound silly, but how do i go about installing them? No idea where to put them.
thanks,
tom
Hey Jerome,
Appreciate the reply. I’ve placed them there, but still no luck.
Also i tried building a simple arm joint. Turns out it doesnt build fine, i must have overlooked it 
but here is the script editor dump from a clean scene.
GEAR version : 3.2.0
= SHIFTER RIG SYSTEM ==============================================
= GUIDE VALIDATION ==============================================
Checking guide
Get options
Get controllers
Get components
arm_C0 (arm_2jnt_02)
Find recursive in [ 0:00:00.039699 ]
Get parenting for: arm_C0
Guide loaded from hierarchy in [ 0:00:00.040673 ]
= BUILDING RIG ==============================================
Initial Hierarchy
Init : arm_C0 (arm_2jnt_02)
Objects : arm_C0 (arm_2jnt_02)
appreaciate all the help 
Can you please run this on the script editor (python) and see if it works please?
import pymel.core as pm
node = pm.deformer(type="mgear_curveCns")[0]
hey Jerome,
I get this error when i run the command.
also this is the start up log on a fresh scene.
file -f -new;
// untitled //
commandPort -securityWarning -name commandportDefault;
onSetCurrentLayout “Maya Classic”;
// Warning: file: /Users/Elson/Library/Preferences/Autodesk/maya/2019/prefs/filePathEditorRegistryPrefs.mel line 4: filePathEditor: Attribute ‘aiImage.filename’ is invalid or is not designated ‘usedAsFilename’. //
// Warning: file: /Users/Elson/Library/Preferences/Autodesk/maya/2019/prefs/filePathEditorRegistryPrefs.mel line 5: filePathEditor: Attribute ‘aiPhotometricLight.aiFilename’ is invalid or is not designated ‘usedAsFilename’. //
// Warning: file: /Users/Elson/Library/Preferences/Autodesk/maya/2019/prefs/filePathEditorRegistryPrefs.mel line 6: filePathEditor: Attribute ‘aiStandIn.dso’ is invalid or is not designated ‘usedAsFilename’. //
// Warning: file: /Users/Elson/Library/Preferences/Autodesk/maya/2019/prefs/filePathEditorRegistryPrefs.mel line 7: filePathEditor: Attribute ‘aiVolume.filename’ is invalid or is not designated ‘usedAsFilename’. //
// AbcExport v1.0 using Alembic 1.7.5 (built Feb 7 2018 13:51:52) //
evalDeferred “shaderBallRendererMenuUpdate”;
// Warning: line 1: filePathEditor: Attribute ‘aiStandIn.dso’ and label ‘Standin’ have been saved already. //
// Warning: line 1: filePathEditor: Attribute ‘aiVolume.filename’ and label ‘VDB’ have been saved already. //
// Warning: line 1: filePathEditor: Attribute ‘aiImage.filename’ and label ‘Image’ have been saved already. //
// Warning: line 1: filePathEditor: Attribute ‘aiPhotometricLight.aiFilename’ and label ‘IES’ have been saved already. //
import arnold
// Successfully imported python module ‘arnold’ //
import mtoa
// Successfully imported python module ‘mtoa’ //
import mtoa.cmds.registerArnoldRenderer;mtoa.cmds.registerArnoldRenderer.registerArnoldRenderer()
// Successfully registered renderer ‘arnold’ //
updateRenderOverride;
// Warning: file: /Applications/Autodesk/maya2019/Maya.app/Contents/scripts/startup/autoLoadPlugin.mel line 35: Loading plug-in “mtoa” has resulted in changes to the scene that may need to be saved. //
// AbcImport v1.0 using Alembic 1.7.5 (built Feb 7 2018 13:51:52) //
updateRendererUI;
updateRendererUI;
Yeah so the solvers aren’t loading correctly. Hmm…
Can you please paste the mGear lines from your Maya.env just to double check for any problems?
There is a chance either there is a problem with your installation, or those compiled solvers are not working properly on your system. I don’t have Maya 2019 installed so I can’t test for you, but if we don’t figure this out today, I’ll go and install it and test them on my side.
(Meta: When you post code, you can put it between 3 backticks, or in a code block and it will format more nicely.)
Oh, I think I might know.
I believe the plugins should be inside a directory called plug-ins. In your screenshot you put them directly under x64
