Shared Settings

MRS : Landing | Members | Queue | Forum | DocsLibrary | How

Last Updated: 2.28.2019

These are shared attributes that are not uncommon between multiple rigBlocks



bool | Whether to add a cog helper to our rigBlock


enum Where we want our rigBlock to attach to it’s blockParent

  • base |  0 index on the blockParent
  • end | -1 index on the blockParent
  • closest | closest joint/dag on the blockParent
  • surface – NOT IMPLEMENTED


float3 | The stored base size values on a given rigBlock



enum | What shape to use for our loft. We’ve got a number of options

  • TriNeg[1]
  • TriPos[2]
  • TriDown[3]
  • TriUp[4]
  • Digit[5]
  • SquareRoundDown[6]
  • SquareRoundUp[7]
  • SquircleDiamond[8]
  • WidNeg[9]
  • WidePos[10]
  • WideDown[11]
  • WideUp[12]
  • Circle[13]
  • SquareNeg[14]
  • SquarePos[15]
  • SquareDown[16]
  • SquareUp[17]
  • Squircle[18]
  • SquircleNeg[19]
  • SquirclePos[20]
  • SquircleNeg[21]
  • SquircleUp[22]
  • Diamond[23]
  • Square[24]

Here are some arm limbs of circle and square type.


enum  | Pick the start (lever) or end (foot/pad) loft shape.


enum datList  | Option to set the loft shape per handle.


enum  | Pick the kind of loft setup you want

  • default | One shape for all handles
  • loftList | See above


enum  | Linear/cubic loft


int | Number of sides for the loft. Only visible with cubic mode.


int | Sub split on the loft


int  | The number of controls for a given block. Note, you must change setting and rebuild template to see changes.


int  | The number of shapers for a given section or block to help define it

On Limb this acts as numSubShaper does on Segment

Note – you must change setting and rebuild template to see changes.


int  | The number of sub shapers between each main shaper



int  | A main value for how many roll joints per segment of joints.


int/datList  | A datList chain of attributes to set the roll count per segment of our LIMB. Currently


Settings for the rig setup type.


enum  | What kinda of ik setup for this particular rigBlock

  • none – No IK
  • rp – Rotation plane setup
  • spline – Not fully implemented as ribbons work for the most part. Future proofing
  • ribbon – Uses our ribbon setup which has a myriad of options


enum  | The kind of ik base we want.

  • none – No special base setup
  • cube – Cube shape base (depreciating)
  • simple– Simple handle at the end
  • hips – Does some special setup to have have localized hip control on the segment


enum  | The kind of ik end we want.

  • default | Simple ik end shape. Cube created at end of the ik chain
  • bank | bank setup added at the end of the block
  • foot | Assumes you will have at least a ball. Single Toe setup possible too
  • pad | Assumes animal like setup with a bank
  • hand | Future proofing for hand setup we want to do
  • tipBase | IK pivot at the second to last prerig handle
  • tipMid | IK Pivot at the mid point of the chain
  • tipEnd | IK Pivot at the end of the chain

Images coming…


The foot setup can be done with  hasEndJoint

or not…


bool  | Toggles whether to setup aim down closest axis setup to the ik controls of the rigBlock.

At rig setup, the last prerig handle is used to figure out the closest vector to a world axis. This rotation value is used as zero for that control and there is an extra setup to allow for non zero reset values on control’s base transforum attributes.


int  | number of space pivots to use for controls. When 0, they won’t be added but constain groups will replace where those would have been


bool  | Whether to use proxyShapes for direct controls where possible


enum  |

  • none – just attach to the ribbon with no aim
  • stable –  stable aim down the chain
  • stableBlend – Blended aim down the chain where every joint except start/end blend their aim forward and back. This option sometimes gives better results


enum |How we want our rig dags to connect to our ribbon.

  • constraint – connect by constraint
  • matrix –  NOT IMPLEMENTED


enum  |

  • fixed -Fixed attachment to our ribbon
  • floating –  Float on the surface in an even distribution
  • blend – Add option to blend between two


enum  | Which direction from the settings targed position we want our settings cast relative to the joint axis.

  • up
  • down
  • out
  • in

Note – On a left limb, the out /in would be reversed


enum  | Where we want this rigBlock’s setting placed at rig time

  • start
  • end
  • cog – just use the cog shape. Used on default spine for example


bool  | Whether to setup space switching on direct controls

Not sure on the speed hit on this so have it off by default.


bool  | Whether to setup for scaling


enum  | Options for seeing up squash and stretch

  • none – no squash stretch setup
  • Simple – only use aim measure
  • Single – single channel measuring (out)
  • both – independent channels. Churro squash/stretch


bool  | Whether to wire up ability to turn off squash stretch and set scale factor per joint


bool  |

  • None – no squash setup
  • arcLength – Use a curve to measure the length of the segment as it’s more consistent than
  • pointDist – Per joint measuring on aim


float  |Peak influence on squash and stretch on the segment chain. Most often 1


float  | Minimum influence on the squash chain. Use 0 if you want the start and end to have to squash stretch from the


bool  | Whether to show our measure nodes on our rigBlock.


Settings for post processes.


bool  | Reverse the normal on the lofts. Because maya is consistently inconsistent with lofting. Between sessions. It’s nutty.


enum  | What kind and whether you want a proxy geo root

  • none | Nothing.
  • loft | Our current default
  • ball | Simple sphere

Road Map

  • attachPoint | surface –

Josh Burton

[MRS Project Lead | CG Monks] Josh is an animator turned TD who hails from Oklahoma, pre-undergrad in the Marine Corps, animation basics at Savannah College of Art and Design, cut his teeth in gaming and commercials before co-founding CG Monks and more recently the CG Monastery. The Morpheus Rigging System is a culmination of years of R&D and he is now thrilled to see what users can create, collaborate and expand on with this open source MRS platform.