Archive for the 'Initial Setup' Category

Thu, Apr 14th, 2016
posted by jjburton 08:04 AM

This post is to remind us how to do this. J had a computer issue and had to reinstall Windows:)

  1. Follow this tutorial –
  2. Make some coffee, you earned it.

If you get the “server’s host key is not cached…” error when attempting to push from SourceTree:

  1. Command prompt
  2. Go to Program Files (x86)/PuTTY
  3. “plink -agent”
  4. Hit ‘y’


Wed, Jul 11th, 2012
posted by jjburton 09:07 AM

Short and simple vid this week on how to install the tools. Prolly should have done this a while back.

Work has been coming along with the rigger, gotta say my rudimentary code from last year is just lousy. That’s why we learn and grow, no?

If you’ve missed it, we’re lookin for feedback on where to proceed next. If you’d like to give us your input, please fill out the form here:


Tue, Mar 27th, 2012
posted by jjburton 01:03 PM

So at least to me, the maya.env setup has perpetually been an exercise in frustration. For years, it seemed it would remain shrouded in mystery. Recently as I’ve been making tools and learning I took some time to do some googling and I have a much better understanding of how to make it work  well so you don’t have to!

So, let’s set it up…

Homework first!

  1. Find your maya folder where your maya.env resides
    On a typical pc install, that will be ‘ \My Documents\maya\%version\’. In my case, it’s ‘X:\My Documents\maya\2011-x64’
  2. Remember where you installed the cgmtools repository to

Let’s get to it.
Note – this is for a Windows setup

  1. Make sure Maya is closed
  2. The first thing we wanna add is an inline variable we can call. This doesn’t have to be done but with multiple repositories, I found it easier. We’ll add this to the top
    REPOSPATH = X:/repos/
  3. Then if you already have some paths on Maya_Script_Path or PythonPath, you can amend them by putting the following at the end of each one followed by a ‘;’
  4. Open up Maya and type the following in a mel command line:

Here’s an example of a clean maya.env with no other paths added.

[crayon]REPOSPATH = X:/repos/



Thu, Mar 22nd, 2012
posted by jjburton 03:03 PM

For users granted access to the repository for up-to-date tools and code this is run down on getting setup. Eventually we hope to have this all happen within Maya but for now, there’s some leg work. At present, we’re using as our code repository in the git format. This is tailored to a pc user, if we get it figured out for others, we’ll add that here.

For a great immersive, tutorial on learning git, check out gitimmersion.

For the everyday pc user…

  1. Sign up for a bitbucket account.
    If you have one already, move along…
  • Go through the tutorial to get a foundation on how stuff works.
  • At a minimum, you need to install msysgit from the tutorial. We only need step one install stuff
  • Get git permssion
    For now, this is a invitation only thing. You’ll get an invite to the repository after which you can connect to it
  • Decide where you wanna store stuff
    For myself, I created a ‘repos’ folder on my ‘x’ drive as I sync to several repositories. So my path I’ll be going to via gitBash
  • Get the git path
    If you have permission, you can go to bit bucket and see the path to sync to to clone the repository
  • Sync it up!
    1. Open git bash
    2. Browse to your directory to store stuff
    3. Type in the clone command
    4. Put your password in
    5. Let it finish up and you should see something like…
      gitBash install step screengrab
  • Check your work
    Make sure it pulled everything
  • Updating anytime is relatively straight forward anytime you please.
    1. Git bash to the cgmtools folder
    2. Type the following:
      git checkout
    3. Input your password and let the download finish
    4. Have a chocolate, you deserve it!

    After you’ve done this step, time to setup your maya.env

    Thu, Mar 22nd, 2012
    posted by jjburton 07:03 AM

    …with as little hair pulling as possible…

    So, setting up an IDE for doing coding is a pretty good idea if you’re gonna be doing a lot of it. My IDE of choice is Wing and it can be a little tricky getting things setup right for auto-completion. If you wanna get going with it, you can…

    1. First download it from their site
    2. Add maya’s mayapy exec as a custom Python Executable in Project Properties>Enviornment
    3. Add your repository as a custom Python path in the same section – in my case ‘J:\repos\cgmtools\mayaTools’
    4. Next see their doc page for maya for help
      1. I had to change one item for my own setup. Maya 2011’s pi file location ended up being:
        C:\Program Files\Autodesk\Maya2011\devkit\other\pymel\extras\completion\pi
    5. Add your own computer’s path in Preferences>SourceAnalysis>Advanced>Insert and put that path in there and you should be golden
    If you have to generate your own pi files for whatever reason…
    Start with the tutorial here to get you most of the way there.
    1. Now, when get to the the part about the genmayapi thing, you’re gonna wanna edit it cause it won’t work off the bat depending on your version of Wing.
      1. Lines 5 and 7 will need to be modifed to your version of Wing. In my case, it was ‘Wing IDE Personal 4.1’
      2. Line 12 will again need soe work, in my case it was ‘Wing Personal 4’.
        You can find the folder directly in windows at  C:\Users\%Name%\AppData\Roaming.
    2.  After those fixes you should be able to run the genmayapi and finish out the tutorial without issue.
    This was my

    [crayon]import os
    import sys
    import maya.standalone

    WING_DIR = r’c:\Program Files (x86)\Wing IDE Personal 4.1′
    if not os.path.exists(WING_DIR):
    WING_DIR = r’c:\Program Files\Wing IDE Personal 4.1′

    sys.path.append(os.path.join(WING_DIR, ‘src’, ‘wingutils’))
    import generate_pi

    PI_FILES_DIR = os.path.join(os.environ[‘AppData’], ‘Wing Personal 4’, ‘pi-files’)
    MOD_LIST = [

    def main():
    for mod in MOD_LIST:
    pi_filename = os.path.join(PI_FILES_DIR, os.sep.join(mod.split(‘.’)) + ‘.pi’)
    if not os.path.isdir(os.path.dirname(pi_filename)):

    print ‘Generating .pi file for’, mod

    f = open(pi_filename, ‘w’)
    generate_pi.ProcessModule(mod, file=f)

    if __name__ == ‘__main__’:

    Happy coding!