Skip to content

[BUG] control_01 "orientation" connector broken #578

@timothyliu3d

Description

@timothyliu3d

🐞 Bug Report

Description

When using the "orientation" connector type in control_01 or EPIC_control_01 components with multiple refarray targets, the resulting rig build is broken instead of preserving offsets.

Steps to Reproduce

  1. Create 3 control_01 components (or EPIC_control_01 components).
  2. Uncheck "World Space Orientation Align" in each of their settings.
  3. Place the comp roots in any arbitrary position and rotation.
  4. In control_C0 component settings, change connector type to "orientation".
  5. Add the other 2 components as "IK Reference Array" targets.
  6. Build rig.

Expected Behavior

control_C0 should maintain its current world matrix after rig build, as well as when switching the control_ikref attribute. This is the expectation when creating a "rotate space" setup.

Actual Behavior

control_C0 is snapped to an odd orientation instead of matching the component guide.

Maya Version

  • Maya Version: 2026
  • OS: Windows 11

mGear Version

  • mGear Version: 5.1.0

Error Log Formatting

N/A

Additional Context

Bug seems to come from shifter.component.Main.connect_orientCns, where it uses pm.orientConstraint(..., maintainOffset=True); this does not work with multiple targets.

However, it looks like the solution is already implemented as .connect_orientCns2 in the same class, but is unused.

Use case wise, I'd imagine .connect_orientCns2 is the typical expectation.

Current workaround using "official" mechanisms is to, for each target, build a dummy control_01 component, then locking/hiding them in a post-step.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

Status

WIP

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions