Skip to content

Shotgun Default2 Configuration v1.1.8

Compare
Choose a tag to compare
@mathurf mathurf released this 16 May 18:06

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]