Dave Girard's 101 Autodesk® Maya® Tips is now available in Kindle, interactive iPad edition and DRM-free EPUB/PDF editions. Work faster, cry less. Read more about the ebook.




Follow cgbeige on Twitter

Topics by tag:



Recently published articles by Dave G:



Free downloads by Dave G:



Mac OS X-only downloads:

Mac Maya Users: Speed Up the Viewport by Hiding the Help Line

So, after a discussion on CGSociety about a viewport lag that was introduced in Maya for OS X after version 2011, it seems that the culprit is the Help Line. Until this bug is fixed, you can give Maya 2012 and later a slight bump in FPS on OS X by hiding the Help Line. Now someone needs to find out how to fix the f, [ and ] hotkeys that stop working – that plagues all platforms and it’s super annoying.

3 notes | Permalink

Maya/Mudbox/Autodesk 2014 App Users: Don’t Upgrade to Mavericks Quite Yet

Update: fix for Maya 2014 released: grab it here.


Just a small warning about OS X Mavericks that should hopefully prevent some unwelcome headaches for people running Autodesk 3D apps on OS X. I am running Mavericks now and did some testing with the betas and, while all previous versions work fine (2013 included) there is a critical issue with Adlm (the license software) and the 2014 Autodesk products that prevent them from activating. It’s fine if you upgrade an existing OS X install that has the programs already activated but it will fail to activate new licenses for Maya 2014 or Mudbox 2014, etc. This has to do with how the FLEX license manager does weird stuff to try and hide licenses from your OS in a partition, from what I understand. It’s a hack to allow demos that time out. Autodesk knows about it and is releasing a fix any day now – I’ll update this post when it’s released.

Otherwise, I would say that, if you are fine with your system now, you might want to wait a few weeks because there are a lot of changes to OpenGL in Mavericks that could affect your system or apps. You get a warning that the Adobe Creative Cloud software isn’t supported yet but Photoshop CC works fine on my end. Anyway, I need Mavericks for Mari and AMD support on OS X. It’s a solid release and has some amazing tech in it – read here for all full rundown and review. I would just be careful before fixing what isn’t broken until the kinks have been worked out. I know that Mari tessellation preview for AMD cards, for example, is in need of a bug fix that’s coming soon as well. I’ve also heard of one Nvidia user having issues with ZBrush but it works fine for me. But I definitely recommend the upgrade. OpenGL 4.1 is finally included and the upgrade is completely free. If you’re on a mobile machine, the extra battery life is great and pros will benefit from better multi-monitor support, SMB 2.0 inclusion and tag metadata, to name a few things. But, if you want to be extra safe and prevent the new OS’ power saving features from tinkering with your graphics apps, consider turning off App Nap in the program’s Get Info panel:

As I mentioned before, the Library folder for your home directory can now be re-shown in the Get Info panel for the Home folder too. If you have applications like Windownaut that depend on Access for Assistive Devices, that has been moved to the Security and Privacy preference pane:

Anyway, stay tuned for my eventual Xeon E5 V2 Mac Pro 2013 review for Ars Technica. Apple said that machine is coming in December.

3 notes | Permalink

Quick L’Ecorché Desktop for OS X Review – You Need This

If you work on character design or with figure sculpting, it’s crucial to have an anatomy reference on hand. The respected anatomy app L’ecorché came out a while ago for iPad and iPhone but yesterday my iPad was in my painting studio and I wanted access to L’ecorché while I sculpted in ZBrush and thought “wouldn’t it be great if they had a desktop version?” So I checked online and was pleasantly surprised to find it exists in Mac OS X application form. So I bought it and here it is with it’s resizable window and even a handy library of bone diagrams:

One of the nice benefits of the popularity of the iPhone and iPad is that it is pretty easy for people port the Cocoa code from those apps to OS X. Usually this just means there are a lot of cheesy Gameloft mobile games available in desktop wrappers, but this is one of those good exceptions. As a program, it makes perfect sense and the OS X version has the ability to float on top of other apps – perfect for sitting over the ZBrush window while you sculpt:

At $5, it’s also an amazing price for the service it provides. Since it’s sold on the Mac App Store, you get a license for all of your Macs, so you can sculpt on the road or on a desktop and only have to pay for it once.

My only complaint about L’ecorché Desktop is that the navigation scheme is not standard so you spend more time getting accustomed the rotation/zoom setup than you should. There should be an option for Maya/Cinema4D/Mari.- or ZBrush-style navigation. Also, the rotation orbit locks on axis a little too easily. If the program’s developers are reading this, I’d like to request a full borderless mode toggle so you can hide all outside interface elements when floating the application over much-needed screen real estate in ZBrush.

Otherwise, if you’re on OS X and do any work with figures or you just want a reference application to complement your dusty copy of Bridgeman’s Life Drawing, look no further. Get this now.

2 notes | Permalink

"Show Library Folder" Shows Up in Mavericks Finder

I was just changing my home folder’s icon settings in the Mavericks beta and stumbled on something that I haven’t seen mentioned in any of the OS X 10.9 coverage: the option to show the ~/Library folder. Open your home folder and then open the Get Info panel and…

Rejoice! Newbs will no longer wreak havoc on their application settings by deleting it and power users will no longer have to use “chflags nohidden ~/Library” every time they install a system update that rehides it.

2 notes | Permalink

Using the Clipboard as a Working Buffer: Automator for Apps that Don’t Support Automator

If you use a text editor like TextMate, BBEdit or even Chrome in OS X, you get full support for Automator’s text replacement features but some applications don’t use the Cocoa classes for their text boxes so they don’t get access to these. Nevertheless, there is a good workaround for these cases when you want to filter text in one of these Automator-unaware applications: send the clipboard to your Automator script and send the output back to the clipboard. As I mentioned in my recent Ars Technica article, OS X has a ton of command line applications to bridge the GUI and cl (open, say, etc) and they have two built-ins for clipboard manipulation – “pbcopy” and “pbpaste” – which can be used to send text to the clipboard (pbcopy) or echo the clipboard into stdout (pbpaste). So, if I want to take some attribute text from the Maya Script Editor and turn it into a variable, it’s easily done by using this clipboard buffer setup in an Automator service:

See it in action:

That service can be bound to a hotkey in the Keyboard panel of the System Preferences for extra speediness.

1 note | Permalink

A Future-Proof Automator Service to Launch a Maya Instance

If you want to run another instance of any program on OS X, you have to do it from the terminal with the “open -n” command. I have an alias in .bashrc that will do this for Maya 2014:

alias 2014=’open -n /Applications/Autodesk/maya2014/Maya.app’

So, when I type “2014” in the terminal, it opens another instance if Maya is already running. But, since I tend to run both older versions on occasion alongside betas, I thought I’d make something a little more flexible with an input launch whatever version. So I made an Automator service to launch another instance with a prompt for the version you want to launch:

Download the Automator Service here. If you want to change the default version in the text input field, just open it in Automator and change it yourself. Future proof.

1 note | Permalink

Creating the Ultimate Creative User OS: My Ars Technica Article

I wrote a piece for Ars Technica about how to build the ultimate creative user-oriented OS by taking parts from all the big dogs of the OS world. Check it out.

1 note | Permalink

It Lives! Mac Mari beta

Just got my invite to the Mac Mari beta and excited to be running this app – on even my 17” MacBook Pro:

Can’t wait to get it running on new Mac Pro.

0 notes | Permalink

Maya Scripting 101: Avoid Common Names for Global Variables

I just spent the last half hour trying to find a conflict with V-Ray Tuner and someone else’s MEL script for Maya. As soon as I opened theirs, it reminded me of the main thing you should do when learning to script: avoid common words for global variables. If you open open script that relies on $text as a global variable and open another that uses the same global variable, they are both going to break. This script I looked at was peppered with global variables with cosmically stupid names like $text, $parent, $node and $p. I’m embarrassed to say that I had $obj as a global variable in V-Ray Tuner, so I’ll need to change that since it’s a common one.

If you’re on OS X or Linux and want to see all your global variables in a script file, this command will show you them:

cat /path/to/MELfile.mel | grep global | grep -o -i '\$[A-Z]*' | sort | uniq

That will spit out something like this:


$buildDirtShader
$cammy
$composite
$copyMesh
$currentRenderLayer
$dirtPass
$domelightVRay
$dummyCubeYo
$dummyCylinderYo
$dummyPlaneYo
$dummySphereYo
$fileResulter
$gammaCorectBakes
$homeNameCammy
$homeNameCammyNew
$homeScriptDir
$inputter
$keepMatsFinished
$keylightTooVRay
$keylightVRay
$moveAOStatus
$myStoreTexture
$myTempVRayMatSelection
$obj
$preBakedDiffuse
$saveNewSceneCheck
$storedMaterial
$surfaceShaderTempV
$tempRL

I’m increasingly trying to get into the habit of appending some two-character nonsense onto the end of dumbly-named global variables so, instead of $node, it’s $nodeYo, which is much less likely to exist elsewhere because no one else codes in Jive talk.

Can you dig it, home?

2 notes | Permalink

Automator Workflow to Migrate Maya ASCII/Nuke/plaintext Files to Another Disk

I am just moving my work to a new Lacie 2big Thunderbolt enclosure and wanted to save myself annoying task of migrating all my existing work to link to the new disk in place of my old one. There are nice utilities like FileTextureManager for Maya and Nuke has a find/replace that do this on a per-scene basis but this seemed slow since I would be doing the exact same replacement for all future files.

So I made an Automator workflow that reads plain text files and substitutes my “dullard/WORK_mbp” path in the file with “lackey/WORK” and then creates a new file next to the old one so nothing is clobbered. Since Maya ASCII and Nuke files are plain text, the script can use the Unix utils awk and sed as if it were just working on a big (and quite boring) essay.

See it in action:

Grab the Automator workflow here. Obviously, you’ll need to edit the workflow in Automator to substitute your paths instead of mine:

The text between the % are the find and replace terms. The script doesn’t overwrite any files but just for the sake of legalese, it comes with no guarantees.

0 notes | Permalink