Shotgun Basic Configuration v1.1.15

What’s new?
Added support for distributed configs in the setup wizard, as well as a number of improved features and bug fixes, including:

• Introduced the standalone publish API, and
• Resolved issues around project filtering with the Software entity.

Features/Polish

• Added support for distributed configs in the setup wizard. [SG-8474]

  • We added a new dialog to choose between a Distributed or Centralized setup.
    

  • There is a new app, tk-multi-devutils, which will be available when running a distributed setup project. The “New config sandbox...” option will be available after you select your project inside Shotgun Desktop. This replaces the Clone configuration actions, which are not available for distributed setup.
    

  • When selecting the “New config sandbox...”, a new dialog will open to create your config sandbox.
    

  • New tools will be available within your created config sandbox.
    

  • It will be now possible to do core and config updates directly from Shotgun Desktop.
    

• Introduced the standalone publish API. The standalone publish API allows you to do the same operations in a script that you can do with the Toolkit application. As such, you can entirely automate the publish process without any user interaction or use it on a render farm in order to automate the publication of rendered jobs. [SG-7260]

• Added the post phase hook, which allows you to do some post-processing after validation, publish and finalize. [SG-2871]

• Publisher log messages in the UI are now colorized. A big thanks to Joe Hultgren for his contribution to this feature. [SG-9236]
  

• Cloning repositories on Windows will now display a terminal only if authentication is required with the Git server. [SG-4824]

• Updated some third-party libraries of tk-framework-desktopserver. [SG-9003]

Bugs

• There were issues around project filtering with the Software entity. This fix ensures the project filtering is working fine either with no engines associated or when two software with the same engine use different project restrictions. [SG-4623]
• There was an issue where a cached configuration was always considered out of date and therefore always deleted and rewritten when bootstrapping. The fix ensures we are are not rewriting a cached configuration over and over again. [SG-8646]

Shotgun Basic Configuration v1.1.14

What’s new?

Bugs

The Maya plugin's bootstrap routine contained a thread safety problem related to progress reporting that could cause Maya to crash or hang at startup. This fix ensures this logic is now always run on the main thread to improve stability during bootstrap. [SG-9012]

Shotgun Basic Configuration v1.1.13

What’s new?
Added Mp4 to valid extensions for Loader2 and Shotgun Panel apps, as well as a number of improved features and bug fixes, including:

• Added documentation for core hooks to the reference documentation, and
• Added ability to set hotkeys in the tk-nuke.yml settings file.

Features/Polish

• Added documentation for core hooks to the reference documentation. [SG-6464]
• Added ability to set hotkeys in the tk-nuke.yml settings file. A big thanks to Anthony Kramer and CBFX for his contribution to this feature. [SG-7622]
• Added Mp4 to valid extensions for Loader2 and Shotgun Panel apps. [SG-7631]
• Introduced a new core hook called Bootstrap that can be used to cache Toolkit bundles from another location than the original one, i.e. Git or the Toolkit AppStore. [SG-7596]
• Added items name in publish completed and finialize complete messages. [SMOK-48149]
• Made some changes in tk-photoshopcc engine to reduce considerably the risk of a filename length issue on Windows. [SG-7965]
• Added some tweaks in tk-core to the Link and LinkVisited colors provided by the palette used in Qt5 environments. [SG-6442]
• Allows a parent object to be given when bootstrapping asynchronously. [SG-8369]

Bugs

• There was an issue in Shotgun Desktop where you can get some missing app launchers. This fix ensures the application will now skip over undownloadable software icons instead of failing and not showing them. [SG-8274]
• There was an issue with the Shotgun demo app where python can crashed on exit. This fix various thread-leaking issues that caused some stability problems in some environments on close. [SG-6409]

Shotgun Basic Configuration v1.1.12

What’s new?

Features/Polish

• Updated third-party modules used by the browser integration.

Shotgun Basic Configuration v1.1.11

What’s new?
Official support for Nuke 11.2, as well as a number of improved features and bug fixes, including:

• Updated the Python API to 3.0.37,
• Resolved issues when running Nuke in no-display mode, and

Features/Polish

• Official support for Nuke 11.2. [SG-7668]
• Updated the Python API to 3.0.37, which includes a new preferences_read method and fixes around non-ASCII file names when given to various upload methods. [SG-4483]

Bugs

• There was an issue causing the engine.context_change() to fail when running Nuke in no-display mode. This fix ensures that context changing works correctly in no-display mode. A big thanks to Sai Aparna Ramamurthy and Digital Domain for her contribution to this bug fix. [SG-7331]
• There was an issue with the Shotgun panel when running Nuke in no-display mode. This fix ensures we no longer attempt to navigate the panel in no-display mode. A big thanks to Amy Ahronek and Netflix for her contribution to this bug fix. [SG-7626]

Shotgun Basic Configuration v1.1.10

What’s new?
Official support for Photoshop CC 2018, as well as a number of improved features and bug fixes, including:

• Resolved Shotgun integration issue in Houdini 16.5.481+ on Windows,
• Resolved Workfiles2 hierarchy view disappearing when the my tasks checkbox is selected, and
• Resolved Loader2 reload feature spinning forever.

Features/Polish

• Official support for Photoshop CC 2018. [SG-7145]
• We now use more reliable means of finding the first video track in an openclip file produced by Flame in Nuke. We also preserve the openclip version number during our update of its contents. [SG-6781]

Bugs

• In Houdini 16.5.481+, Shotgun integration was broken on Windows because of a Qt dialog raising fatal error. This fix ensures that Shotgun integration is working fine with latest Houdini 16.5 production builds. A big thanks to Craig Barnett and Falcon’s Treehouse for his contribution to this bug fix. [SG-7314]
• Loader2 reload feature was spinning forever. This fix ensures reload feature is working fine by implementing a hard_refresh method on the publish type model. [SG-6836]
• There was a bug where Project Filesystem Folder would not be displayed in the Shotgun Desktop menu for projects configured through the Advanced Project Setup. This fix ensures the Project Filesystem Folder is correctly displayed in the Shotgun Desktop menu. [SG-6816]
• Photoshop CC could sometimes be in the wrong context if a document was opened before the engine completed its initialization. This fix ensures we are always in the right context. [SG-6662]

Shotgun Basic Configuration v1.1.9

What’s new?
New Import Clip published file action for Nuke Studio and Hiero, as well as a number of improved features and bug fixe, including:

• Resolved built-in Houdini pypanels being removed from the Python pane menus when Toolkit is used, and
• Resolved publisher randomly failing during publishing.

Features/Polish

• Certain types of publishes (images, image sequences, etc.) can now be imported into Nuke Studio and Hiero as clips via the Loader2 or Shotgun panel apps. A big thanks to Brice Lefebvre and Digiteyes Studio for his contribution to this feature. [SG-5387]
• Added support for rendering a Flame write file node without having pre-created a shot in Shotgun. [SMOK-48641]

Bugs

• Publisher randomly failed during publishing. This fix ensures Publisher is not failing anymore by reacquiring the parent pointer just before processing. [SG-4584]
• In Houdini 15+, when you have Toolkit enabled, the 'Shotgun' submenu in the 'New Pane Type' menu was taking the place of Autorigs, Character Picker, and Pose Library. This fix ensures we append our apps to the Python pane menu rather than rebuilding the entire menu definition. [SG-6457]
• In Houdini 15+, Qt printed a warning on panel launch about an issue finding the QCheckbox's check image file. This fix ensures no more warnings show up on panel launch. [SG-6604]
• If a user signed in to Desktop or authenticated TK using a URL with uppercase characters, Shotgun integration would fail to initialize properly during DCC launch. This fix ensures we lower the casing of the URL when going through our existing sanitization routine during login to Shotgun Desktop. [SG-6617]
• Flame Shotgun Export was failing with one frame or Virtual source clips. This fix ensures we can successfully do a Shotgun Export with one frame or Virtual source clips. [SMOK-45352]
• Shotgun Panel was crashing on launch when script key authentication was used and the current OS user didn’t match a Shotgun user name. This fix ensures that Shotgun Panel is working fine with script key authentication. [SG-4556]
• There was an issue where the background task manager was never properly passed to the shotgunmodel base classes from the hierarchy widget, if it was provided. This resulted in a separate bg task manager being allocated, leading to resource leaks and unclean shutdown. This fix ensures that the background task manager assignment is working fine. A big thanks to Anousack Kitisa and Epic for his contribution to this bug fix. [SG-6700]
• There was a background manager thread-leaking issue in the qtwidgets framework when closing Shotgun app dialogs. This Fix ensures there are no more leaks when closing Shotgun app dialogs. A big thanks to Anousack Kitisa and Epic for his contribution to this bug fix. [SG-6701]
• There was an issue with the visibility option for the accept method of publish plugins. This fix ensures that the publisher now respects the visible entry in the acceptance dict returned by publish plugins. [SG-6463]

Shotgun Basic Configuration v1.1.8

What’s new?
New support for complex filters in Loader2, as well as a number of improved features and bug fixes, including:

• Versioned download links to Shotgun Desktop releases, and
• Resolved slow Houdini launches on Windows

Features/Polish

• Added support for complex filters in Loader2 to be used when setting the tab filters. [SG-5399]
  • Previously you would not be able to add a filter to a tab through the settings that used sub conditions and filter operators. With the update you can now do something like this:

      filters:
            - [project, is, "{context.project}"]
            - filter_operator: "any"
              filters:
                - [entity, type_is, Asset]
                - [entity, type_is, Shot]

• We are now providing versioned download links to Shotgun Desktop releases. [SG-2608]
• We now defer the shelf population by an event loop cycle to resolve slow Houdini launches on Windows. [SG-2898]
• Toolkit dialogs will now display their icon, if available, in the title bar. Note that for certain combinations of OSes and versions of PySide2, the icon may not appear due to bugs in PySide2 and/or Qt5. [SG-5793]
• Toolkit dialogs inside of Flame will now display the new Flame 2019 icon. [SG-4868]
• In PySide2 environments on Windows 10, we were seeing "condensed light" being used for Open Sans when font-weight was set instead of "light". We are now installing font TTF files in reverse-alphanumeric order to ensure that "light" is installed before "condensed light". [SG-4682]
• Makes Publish2 common file info dictionary part of the base collector API. [SG-5389]

Bugs

• As of Nuke 11, there was an issue on Windows where Nuke could hang on its splash screen when launched from Toolkit. This fix ensures Nuke 11 no longer hangs by making sure we no longer import the QWebEngineWidgets submodule from PySide2 on Windows in Nuke 11+. [SG-4782]
• As of tk-houdini v1.5.1, some issues around workfiles2 were reported related to the os.chdir call. This fix changes how we path to a checkbox image in QSS to avoid issues with workfiles2 file open. [SG-5789]
• As of tk-multi-publish2 v2.1.1, it was impossible to select a folder to publish image sequences. This fix ensures we can successfully publish image sequences. [SG-6355]
• As of tk-core v0.18.134, the PublishedFile.path_cache field would not be correctly populated when using a windows local storage with a drive letter on the form X:. This fix ensures that path_cache field always get populated. [SG-6314]
• "Node" type engine commands were not properly handled in Nuke Studio when building menus. This fix ensures we properly handle them. [SG-4609]
• There was an error when selecting the publish description for "Submit for Review" plugin in Nuke. This fix ensures it displays the correct description, and not cause an error. [SG-6358]
• There was an issue where workfiles2 would cause the whole DCC to hang when the user ran the new file action, and had a version folder in the work file template path. This fix ensures that DCCs are no longer hanging. [SG-6431]
• There was an issue where publish would error if the work file save path contained a dynamic folder that needed to be created. It wouldn't check to see if the folder for the new file existed before running the save command. This fix ensures that the work folder exists when saving the scene at publish time. [SG-6429]
• There was an issue where frameworks in bundle.frameworks were named after the descriptor's system name. If a dev or a shotgun descriptor used a different bundle name, frameworks were not correctly recognized. This fix ensures frameworks on app.frameworks are now properly named after the name of the framework dependencies inside an application's info.yml and not after the descriptor's system_name. [SG-5386]

Shotgun Basic Configuration v1.1.7

What’s new?
New storage mapping interface during project setup, as well as a number of improved features and bug fixes, including:

• Using tk-config-default2 as a site configuration to run Shotgun Desktop,
• Adding a local_properties property to publish items for storing data that is specific to the current plugin, and
• Fixing an issue that prevents Shotgun Integration to work in Nuke Studio 9.0.

Features/Polish

• New storage mapping interface during project setup. [SG-2845]
  • The Toolkit Setup wizard will ask you to map each storage root required by the configuration to a local storage in Shotgun.
• Updated the git-based config example we provide in the project setup wizard to use tk-config-default2. [SG-2636]
• We can now use tk-config-default2 as a site configuration to run Shotgun Desktop.
  • sgtk_from_path can now be used with site-wide pipeline configurations. [SG-4715]
  • Better error handling if a pipeline configuration uses a roots.yml but it's project does not have a tank_name set. [SG-4686]
• When unregistering folders via entity type and id, if the entity is retired (or just doesn’t exist), we now suggest to the user that they try to unregister the folder(s) by path instead of by entity. [SG-2818]
• Added local_properties property to publish items for storing data that is specific to the current plugin. [SG-4299]
• Fixed path length issues on Windows. Copying the core into a configuration will no longer carry over tests and documentation. [SG-4717]
• Updated the Python API to 3.0.36, which adds support for downloads and uploads when using SHOTGUN_API_CACERTS and properly handles malware scanning error codes from the server. [SG-4718]
• The Delivery entity is now supported by the folder creation and unregistering. A big thanks to Patrick Macdonald and Halo VFX for his contribution to this feature. [SG-4729]
• A Sgtk.templates_from_path method is now available to retrieve all templates which match a given path. A big thanks to Patrick Macdonald and Halo VFX for his contribution to this feature. [SG-2830]
• Added ability to sort ./tank commands by name when listing all commands. [SG-4783]

Bugs

• Shotgun Desktop was crashing on startup if the desktopstartup framework was locked to an old version or when using an old Shotgun Desktop installer, v1.3.6 or before, for the first time. This fix ensures that Shotgun Desktop does not crash on startup. [SG-4816]
• As of tk-core v0.18.141, a shared core couldn’t be used to launch project actions if site-wide configurations were found that could be used with that project. This fix ensures a shared core can launch project actions. [SG-4798]
• There was an issue that prevented Shotgun integrations from working in Nuke Studio 9.0. This fix ensures that Shotgun integration works fine in Nuke Studio 9.0. [SG-2631]
• There was an issue where folder creation symbolic links did not correctly support references to list fields. With this fix, it is now possible to define symbolic links referencing for example Asset.sg_asset_type as part of the folder schema. [SG-4785]

Shotgun Basic Configuration v1.1.6

What’s new?
Improved Workfiles2 performance with Step filtering for Tasks and deferred queries, as well as a number of improved features, including:

• Updated Shotgun’s integration with 3dsMax for 3ds Max 2019,
• Hook methods for building custom widgets for each processor we provide in tk-hiero-export, and
• New descriptor tokens and multi-level folder creation.

Features/Polish

• Improved Workfiles2 performances with Step filtering for Tasks and deferred queries. [38483]
  • It is now possible to reduce the amount of data fetched from Shotgun for Tasks by only retrieving Tasks for a given set of Pipeline Steps. Step filtering is controlled by a small piece of the application under entity tabs, and is saved in user settings when closing the application and restored when opening it.
  • A new sub_hierarchy setting is now available to run two steps queries, with the second query being deferred until fetching children from Shotgun is really needed—typically when the user expands the tree view. Not systematically fetching a huge amount of data from Shotgun when the application is started can greatly improve performance.
• Updated Shotgun’s integration with 3dsMax for 3ds Max 2019. [46763]
• Provided hook methods for building custom widgets for each processor we provide in tk-hiero-export. This allows for custom preset properties to be created, and those properties then being used to set/initialize the custom widgets. In addition, additional hook methods have been added to allow for customization of if/how Shots, Cuts, and CutItems are created/updated during the export process. A big thanks to Dashiel Bivens and CBS Digital for his contribution to this feature. [46928]
• It is now possible to define Shotgun Entity folder schemas that can span multiple folders. It is also possible to include a regular expression syntax to allow for the extraction of substrings from Shotgun values. This follows the same syntax and format as the subset token in the template system. [46177]
• Path-based descriptors in environment files can now use the CONFIG_FOLDER to refer to the folder containing the configuration files (core, hooks, env) in a pipeline configuration. [46721]
• The clone command has been adjusted so that it will fail quickly if the user does not have permissions to modify/create PC entities in Shotgun, and it'll do so without having copied any data on disk prior to the failure. [46365]
• In Shotgun Desktop, you now see a message saying ”Retrieving configuration…” when downloading zipped configurations from Shotgun. [46567]
• Implemented comparison logic for RPC proxy objects in Photoshop CC. This implements equal (==) and not-equal (!=) magic methods for ProxyWrapper and adds the associated RPC logic to compare the wrapped objects in the remote interpreter. [46593]
• Added support for a tkdeploy file in tk-framework-desktopserver which will be used when uploading to the app store. This file operates similar to a gitignore file and is used to exclude files when the app store zip archive is created. [46849]

Bugs

• There was a high CPU usage issue on CentOS when using PySide 2. This fix ensures there is no more high CPU usage with our integration. [45552]
• There was an issue that caused Shotgun Panel apps to not load when launched from Houdini’s native pane tab menu. This fix ensures the Shotgun panel loads correctly. [46766]
• Flame Assists and Flare were not launching properly with the Shotgun Integration advanced setup auto-path detection. This fix ensures Flame Assist and Flare launch properly. [46557]
• Exceptions raised from executing code were not caught in Shotgun Python console. This fix ensures exceptions are caught and also that they are logged to the engine. [46897]
• In cases where the tank name had a slash in it, and so represents two folders in the hierarchy, it caused an issue where publishes registered incorrectly in Shotgun. This fix ensures publishes in projects where the project contains multiple folders to register correctly in Shotgun. [46674]
• Sometimes, calling show() and exec_() caused a Qt issue where we were getting an invisible modal QDialog, causing the host application to freeze. This fix ensures the modal QDialog is showing up correctly. [46697]
• The Shotgun descriptor using local bundle cache could cause issues with long file names on Windows. This fix shortens the file names used by the Shotgun descriptor to avoid running into the filename length limit on Windows. [46894]
• There was an issue with zipped configurations where a core cached inside it's bundle_cache folder would still be downloaded from the AppStore or Git instead of being pulled from the cache. This fix ensures we are always looking at the cache before downloading a core. [46965]
• There was an issue that prevented the use of procedural hook based evaluation on complex environment properties such as list and dicts. This fix ensures they are correctly handle. [46693]