Skip to content

Shotgun Basic Configuration v1.1.3
Compare
Choose a tag to compare
@mathurf mathurf released this 13 Dec 14:59
v1.1.3
b0c2864

What’s new?

Better support for running configurations from zip files uploaded directly to Shotgun. We fixed a file locking scenarios that could cause an update to fail, improved support for sharing of cache data, and made improvements and bug fixes for Publish2 and different engines and apps.

Features/polish

  • Added expand/collapse indicators to publish items inside Publish2 app. [42707]
  • Added an option to the publish2 summary overlay that allows going back to the publish page after a publish has been performed. [43161]
  • Added display_name and display_action_name settings to the Publish2 app, allowing a TD to configure how it appears on the Shotgun menu. [45881]
  • Configuration option descriptions have been updated in the Advanced Project Setup Wizard. [45869]
  • Added support for new Shotgun fields PipelineConfiguration.uploaded_config and PipelineConfiguraton.sg_uploaded_config, which configurations can be zipped and uploaded directly to. [41416]
  • Thumbnails and Shotgun queries are now cached at the site level, instead of being cached per project, pipeline configuration, and plugin ID. [43294]
  • Added tk-multi-publish2 and tk-multi-loader2 hooks inside tk-flame. [44071]
  • Added Shotgun Site URL on the project context item in the work area information. [45715]

Bugs

  • When in a project with a classic config, if you selected the reload and restart option from the project context menu in the top right, then it would duplicate all the options in the menu. This fix ensures no more duplication happens. [43269]
  • Deleting items prevented them from being dropped again in Publish2 app. This fix ensures you can add them back again. [43561]
  • When a user had no work or published files in their sandbox, and chose to open a work file from another users sandbox, it threw an error. This fix ensures no more errors are thrown and that the file opens correctly. [45463]
  • On Windows there were some file locking scenarios that could cause an update to fail.
    This fix provides improvements and cleanup of bootstrap resolver logic to avoid an update to fail. [45876]
  • With SW entities, the engine name was no longer configured and was not guaranteed to be available to the launch hooks. We now supply the engine name to the hooks. [45898]
  • The version number was missing in the version name after doing a publish from Photoshop CC via the Publish2 app. This fix ensures the version number gets added to version name. [45999]
Assets 2
Loading