Troubleshooting¶

Most problems are one of the few below. When something fails, the Script Editor says why — look there first.

No hotkey is set. A fresh install has none. Set one from the shelf button: Set Marking Menu Hotkey.

The key does something else. Another hotkey, or a newer binding in the same hotkey set, may have taken the key. Open the hotkey dialog: if Current hotkey is empty, set it again; if it shows your key, pick a different one.

You are not over a viewport. The menu belongs to the viewports. Hold the key with the pointer over one, then click.

You changed hotkey sets. The binding lives in the hotkey set that was active when you set it. Switching Maya to another set leaves the menu behind; set the key again in the new set.

The menu shows only what the first selected control can use:

IK/FK, Mirror, Flip, Settings, Select all controls are AM_Rig items. They need an AM_Rig control — or a rig with the attributes listed in Making a rig work with it.
Select child controls and the all below items need a control that has controls below it.
No spaces in the Space submenu means the control has no space attribute yet — see adding spaces.

Nothing selected at all? The menu still opens, with the viewport items only.

"More than one object matches name"¶

Two objects in the scene have the same short name as a selected control — usually two copies of a rig imported without a namespace. The menu opens, but commands that work by name cannot tell the two apart. Reference the rig, or rename one.

A space switch jumped¶

The switch keeps the control's world position by reading it before and restoring it after. If the control is driven by something else as well — an extra constraint, an expression — that restore can be overridden. Check the control's channels are free, not connected.

Add New Space says it cannot find the space group¶

Add New Space needs a <control>_space_cons group above the control. Run Space ▶ Add Space Group on the control first, then add spaces.

weightDriver nodes do not evaluate¶

Was weightDriver ticked in the installer? Run it again and tick it.
Is there a build for your Maya? See the table in Plug-ins.
Is another copy already loaded, from another tool? AM Rig Menu leaves it alone; that copy is the one Maya uses.

Two AM Tools menus, or an old version still loading¶

An install from 0.2.x is still switched on. Run the installer: it finds the old Am_rigMenu.mod and offers to switch it off. Then delete the old folder.

After installing, other AM tools stopped loading¶

That happens when a second AM_Tools was created somewhere else and Maya is now reading the wrong one. Run the installer of any AM tool: it lists every AM_Tools declaration it finds, points out the one in use, and offers to switch the others off. Keep one AM_Tools for every AM tool.