Announcing Tank v0.11

We are really excited to share Tank v0.11 with you! After a long wait, we have finally wrapped up a release with some big exciting new features! We have added QT UI support that works out of the box in Maya. We have added a new experimental motionbuilder engine and we have done lots of small bug fixed and polish. We now officially support multi-engine apps, apps that can run in more than one engine, and we have converted a bunch of our previous apps into multi-apps.

All of the apps and UIs we showed at Siggraph are now available in the Tank app store.

For convenience we have put together a new starter configuration that showcases most of the new features.

Future Releases

Now that we have enabled QT UI support in our main engines, we are switching gears to a more agile approach. We will be releasing much more frequently and functionality will go out in small chunks - an app at a time! We will announce here whenever a new update goes out.


Trying out v0.11

New Tank Clients

If you are just starting to evaluate Tank, it's easy!  The standard configuration that comes bundled with Tank contains a starter configuration that is 0.11 compatible. Just follow the instructions and you'll get all the latest app versions automatically.

If you haven't started up the Tank beta and would like to, drop us a line at to schedule a kickoff.  Also, be sure to stay up to date on the latest Tank happenings by signing up for the announcement list here.

Existing Tank Clients

If you are already running Tank, there are a couple of ways to try out the latest apps in 0.11. First of all you need to get the latest version of the Tank Platform. This is done by running the platform updater script, located in the core scripts folder. This will download and upgrade your Tank install to use the 0.11 Platform.

In order to check for platform updates, do the following:

> cd studio_root/tank/install/core/scripts
> python studio_root/a_tank_project

Once upgraded to 0.11, you are all set to test out all the new apps and engines.

The easiest way to do this is to start a brand new tank project and base it on the latest standard config, attached with this post. This will set up the new project with the latest versions of  apps and engines. If you for example download the attached file to the temp folder, you can set up a new project using the following command:

> cd studio_root/tank/install/core/scripts
> python /tmp/

Alternatively, you can upgrade an existing project to use the latest versions of all the apps and engines. Just run the upgrade script, located in the core scripts folder, and Tank will download and configure the latest versions of all your apps. In this case, the command would be

> cd studio_root/tank/install/core/scripts
> python studio_root/a_tank_project  

If you have any questions about how to upgrade or install, just drop our wonderful support team a line! 


Release Details


  • Added the new tank logo to the action menu!
  • Added experimental motionbuilder support. 


  • The maya engine now comes with a built-in pyside (QT), supporting macosx, windows and linux
  • Improved breakdown app which shows what is out of date in the scene
  • Support for a number of multi-apps (see the new apps section)


  • Improved breakdown app which shows what is out of date in the scene
  • Configurable review app that submits content for review.
  • Support for a number of multi-apps (see the new apps section)


  • The tank app store and default starter configuration now contains an experimental motionbuilder engine!
  • Added a publish app for motion builder
  • Support for a number of multi-apps (see the new apps section)

New Apps

We added a series of new "multi apps". These work in Maya, Nuke and Motionbuilder

  • A set work area app which lets a user change the current work area.
  • A loader app which makes it easy to browser shotgun and load content
  • A recent work app that shows a list of recent work files
  • A summary app which shows information about all currently running apps and engines.

The Tank Platform

  • Optional fields syntax in templates
  • Better handling of core hooks
  • Polished a number of error messages
  • Added new init() method to the engine that runs after all apps have initialized
  • Task assignees can now be mapped to folders in the file system
  • File names in templates can now access any shotgun field as part of retrieving the context
  • A list of invalid values for a template key can now be defined
  • Apps and engines can be enabled and disabled inside environment configs
  • Added support for apps that can run in multiple engines
  • Optimized dependnecy lookups
  • Brand new starter configuration including all the new apps