How Do I Add Multiple Versions of Maya/Nuke to the Launcher or SG Desktop (Using Separate Instances)?

Note: This document describes functionality only available if you have taken control over a Toolkit configuration. Please refer to the Shotgun Integrations Admin Guide if you do not have a more advanced configuration.

The example below walks you through what you need to change in your pipeline configuration to have Maya 2014 and Maya 2015 appear in SG Desktop's launcher and Shotgun as separate buttons or menu items.

config/env/includes/paths.yml

This is where you define the path on the users' machine where the Maya executables live.

Locate the following lines:

maya_windows: 'C:\Program Files\Autodesk\Maya2014\bin\maya.exe'
maya_mac: /Applications/Autodesk/maya2014/Maya.app
maya_linux: maya

Change them to something like this.

maya2014_windows: 'C:\Program Files\Autodesk\Maya2014\bin\maya.exe'
maya2014_mac: /Applications/Autodesk/maya2014/Maya.app
maya2014_linux: maya_2014

maya2015_windows: 'C:\Program Files\Autodesk\Maya2015\bin\maya.exe'
maya2015_mac: /Applications/Autodesk/maya2015/Maya.app
maya2015_linux: maya_2015

config/env/includes/app_launchers.yml

These are the instances of the tk-multi-launchapp (the Launcher) that are configured to launch each DCC.

Note: the "version" specified in the "location" setting below may be different from what you have in your config. You should use the version you currently have, not the version below.

Locate the following lines

launch_maya:
defer_keyword: ''
engine: tk-maya
extra: {}
hook_app_launch: default
hook_before_app_launch: default
linux_args: ''
linux_path: '@maya_linux'
location: {name: tk-multi-launchapp, type: app_store, version: v0.2.14}
mac_args: ''
mac_path: '@maya_mac'
menu_name: Launch Maya
versions: []
windows_args: ''
windows_path: '@maya_windows'

Modify this to look something like this. We're modifying the original instance to make it clear that it's launching Maya 2014, then we're adding another instance with settings configured to launch Maya 2015. 

launch_maya2014:
defer_keyword: ''
engine: tk-maya
extra: {}
hook_app_launch: default
hook_before_app_launch: default
linux_args: ''
linux_path: '@maya2014_linux'
location: {name: tk-multi-launchapp, type: app_store, version: v0.2.14}
mac_args: ''
mac_path: '@maya2014_mac'
menu_name: Launch Maya 2014
versions: []
windows_args: ''
windows_path: '@maya2014_windows'

launch_maya2015:
defer_keyword: ''
engine: tk-maya
extra: {}
hook_app_launch: default
hook_before_app_launch: default
linux_args: ''
linux_path: '@maya2015_linux'
location: {name: tk-multi-launchapp, type: app_store, version: v0.2.14}
mac_args: ''
mac_path: '@maya2015_mac'
menu_name: Launch Maya 2015
versions: []
windows_args: ''
windows_path: '@maya2015_windows'

config/env/project.yml

This is saying that for the project environment, we wish to have the following app launcher instances available.

Locate the following line:

tk-multi-launchmaya: '@launch_maya'

change it to something like this

tk-shotgun-launchmaya2014: '@launch_maya2014'
tk-shotgun-launchmaya2015: '@launch_maya2015'

Modifying existing launcher menu items in Shotgun

Since we've renamed the launchers (from launch_maya to launch_maya2014, etc.) we need to ensure that the places in Shotgun where this menu was showing up, now points to the correct instances. For each of the shotgun environment files, edit the files just as you did above in the config/env/project.yml

config/env/shotgun_<entity_type>.yml

Locate the following line:

tk-multi-launchmaya: '@launch_maya'

change it to the following:

tk-shotgun-launchmaya2014: '@launch_maya2014'
tk-shotgun-launchmaya2015: '@launch_maya2015'
Follow

3 Comments

  • 0
    Avatar
    Marc-Antoine Desjardins

    Hello,

    there is no tk-shotgun-launchmaya in the config/env/project.yml. Has this been replaced by something else ?

    I'm trying to do this for Nuke / NukeX / NukeAssist.

    I did the changes in config/env/includes/paths.yml and config/env/includes/app_launchers.yml, but I'm kind stuck there using this method. I successfully did the simpler one, as it works well with alias, but still, I would prefer this one.

    Thanks

     

     

  • 0
    Avatar
    Marc-Antoine Desjardins

    Oh, sorry, maybe I looked too quickly, it is there now :P

  • 0
    Avatar
    mark pinheiro

    Hi Shotgun,

    As an example that demonstrates configuration for launching DCC apps, it seems quite clear and straightforward. However the Autodesk suite seem to be a slightly different animal to something like the Foundry's Nuke. 

    In the case of Maya you are pointing to two completely separate installs of the same programs which have different names as defined by their year release, and can be treated as two separate entities. Nuke on the other hand installs one executable and then uses flags to define each of the different versions of Nuke. As a result this makes it a little trickier to get Nuke setup.

    Do you have any documentation that demonstrates specifically how to integrate Nuke and all of its available versions, Nuke/NukeX/Nuke Assist/Nuke Studio?

    Thanks

Please sign in to leave a comment.