Skip to content
Rob Blau edited this page Mar 17, 2015 · 114 revisions

Welcome to the release notes for the Multi Launch App. Below you will find an overview of all the changes we did for each release. We try to be as detailed as possible and include all bugs we have fixed, features we have added and things that may have changed. If you have questions about a particular release, don't hesitate to contact our support team!

v0.6.3

Pass multi-launchapp instance to the generic bootstrap.

v0.6.2

improved error when trying to run 3dsmax 2015 with the old tk-3dsmax engine

Details:

3dsmax 2015 requires the newer tk-3dsmaxplus engine to run. However, users may upgrade from older versions of 3dsmax and not realize this. Previously when doing so, they would get an unhelpful error message when the bootstrap script attempted to run on startup. This change catches the error at that point and displays a dialog explaining the need to use the newer tk-3dsmaxplus engine instead.

v0.6.1

App now backups the environment variables before launching an app and restores them afterwards.

Details:

sys.path and os.environ are now backed up before any app launch and restored after so that one app's launch environment can't leak into another's.

v0.6.0

Added generic engine launch logic so new engines do not need to modify this app.

v0.5.4

Documentation Update

v0.5.3

Update the project python bootstrap to reset PATH

Details:

Make sure applications are launched with the proper DllDirectory set.

v0.5.2

Minor adjustments to the Flame bootstrap sequence.

Details:

This changes the way the Flame family is being launched so that it gains greater control over the boostrap and launch process. The actual executable argument is being sent in to Flame so that this can be re-written by the engine at runtime, effectively allowing the Flame engine to run the DCC launch through its own wrapper script. This is to ensure that a particular environment is being set up where all library dependencies are working etc.

v0.5.0

Added support for the Flame Engine.

v0.4.1

Added support for the new 3DS Max Engine supporting MaxPlus and Max version 2015.

v0.4.0

Added support for launching Mari

v0.3.1

Improved error messaging when an application cannot be launched.

v0.3.0

Added a 'defer_keyword' parameter to support some advanced use cases.

Details:

This adds a new manifest parameter called 'defer_keyword'. Here is the manifest description: Advanced parameter. This allows for advanced customization around deferred folder creation. Deferred folder creation allows for the creation of partial subfolder structures depending on a specific keyword (see main documentation for details). Before an app is launched, folders are automatically created and by default (e.g. if you leave this setting as null), the launch app will pass the name of the engine as the deferred folder creation keyword. This makes it easy to set up deferred rules in your folder creation config for tk-maya, tk-nuke etc. However, if you for example wanted to set up specific deferred folder structures for Nuke and Nuke X (both running the nuke engine), you need a finer granularity. This setting can then be used to override the default behaviour of just passing the engine name. Instead, you can pass any string into the deferred folder creation (for example 'nuke' and 'nuke_x' in the case above). This parameter is also useful if you want to use deferred folder creation in conjunction with launching of apps which do not have a toolkit engine defined - for these app launch instances, the engine setting is left blank, and therefore no engine name is passed into the deferred folder creation. In such cases you can utilize this parameter to control the deferred folder creation.

v0.3.0

Added a 'defer_keyword' parameter to support some advanced use cases.

Details:

This adds a new manifest parameter called 'defer_keyword'. Here is the manifest description:

v0.2.19

Relaxed the error catching for the icon setting.

Details: Relaxed throwing an error if the icon is set to a '{target_engine}' replacement string even if the engine setting is empty.

v0.2.18

Support for the icon and versions settings.

Details: Added two new settings, "icon" and "versions". The icon can be used to define an icon that should be registered for the command if the engine has support for icons. The versions setting is shorthand for defining multiple applications where the only difference between the configurations is the version of the application being launched.

v0.2.17

Event log statistics now also tracks the core API version.

v0.2.16

Support for renamed env vars for photoshop engine.

Details: Added support for latest photoshop engine. Added readme for building linux Softimage dependencies. 3dsMax bootstrap handles _blurLibrary not being defined.

v0.2.15

Improved Softimage launching on Linux

v0.2.14

Fixed a bug that would cause launching to fail for 3dsMax and Motionbuilder

v0.2.13

Added ability to launch applications not yet integrated with Toolkit.

v0.2.12

Updated minimum required core version to v0.14.0

v0.2.11

Better support for review versions.

v0.2.10

Added logic for handling launching from review versions.

v0.2.9

Updated Softimage support

v0.2.8

Added exceptions for softimage.

v0.2.7

Houdini is not supported on osx due to Qt compatibility issues.

Details: Houdini is not supported on osx due to Qt compatibility issues.

v0.2.6

Added Houdini and ability to open hiero projects at application startup.

v0.2.5

Renames and support for the new name Sgtk.

v0.2.4

Added experimental support for launching softimage.

v0.2.3

Added a check so that Tasks that are missing steps cannot be launched from when launching from inside Shotgun.

v0.2.2

Adjustments to context handling and folder creation.

Details:

  • The context is now serialized and passed from the app into the booting application
  • Now correctly handles setups which are not task or file based
  • Added new interfaces for better preserving context state when launching from a publish

v0.2.1

Adjustments to context handling and folder creation.

Details:

  • The context is now serialized and passed from the app into the booting application. This means that any context can be transferred into a launching app. Previously there were some built in restrictions as to what was possible to pass.
  • Added a pre launch hook for easy addition of environment variables to the launch.

v0.2.0

Bug fixes and preparation for v0.13

Details:

  • adjusted launch code for hiero to work with latest version of hiero
  • fixed a bug where opening nuke via a nuke file wasn't working
  • general prep for v0.13
  • improved command metadata
  • polish on certain error messages

v0.1.0

Added documentation.

v0.0.2

Fixed issues with launching 3dsmax, removed the platforms parameter from the configs.

v0.0.1

Initial Release to the Tank Store.

Clone this wiki locally