-
Notifications
You must be signed in to change notification settings - Fork 46
Release Notes
Welcome to the release notes for this Engine. 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!
2024-Sep-26
Add support to Nuke 15.1
2024-Sep-09
Rename the use_sgtk_as_menu_name setting to use_short_menu_name
2024-May-7
Add support for Nuke 15
2024-Mar-26
Rebranding component for Flow Production Tracking
2023-Sep-26
Official support for Nuke 14
2023-July-25
Introduces the 'allow_keep_context_from_project' engine setting that avoids the ShotGrid menu from being disabled when for example someone opens a file with Nuke's File --> Open, that does not reside in any known project path. Also Updated latest Nuke supported version to v14.0.
2023-July-25
Introduces the 'allow_keep_context_from_project' engine setting that avoids the ShotGrid menu from being disabled when for example someone opens a file with Nuke's File --> Open, that does not reside in any known project path. Also Updated latest Nuke supported version to v14.0.
Fix error with web login.
2022-Dec-7
Formalizing Python2.6 deprecation, and warn user to restart the DCC when the session got expired.
Fix error with web login.
2022-Mar-28
ShotGrid branding updates.
2022-Jan-21
Updates Nuke version to support 13.1
2021-Dec-1
Replacing shotgunsoftware urls with Autodesk Knowledge Network and ShotGrid Developer Documentation pages.
2021-Jun-01
Rebranded to ShotGrid
2021-Mar-23
Adds support for Nuke 13.0v1 and compatibility with Python 3.
2021-Jan-20
Updating requires core version to v0.19.18
2020-Dec-8
Switches from using the support email alias to pointing to the support site
2020-Nov-05
Fixes an issue where Nuke will freeze on its splash screen if debug logging is turned on.
2020-Oct-06
Bug fix and version support update.
Details:
- Fixes an issue where Nuke would lock up when using apps whilst debug logging was enabled.
- Updates Nuke version to support 12.2.
2020-Jun-09
Nuke startup script updated to be Python 3 compatible.
Details:
The Nuke startup script is now Python 3 compatible, which means a Python 2 build of Nuke can be launched via the tk-multi-launchapp from a Python 3 interpreter. The Nuke engine its self is still not Python 3 compatible however.
2020-Mar-25
Updates Nuke version to support 12.1
2019-Dec-13
Resolves a crash bug tied to panel support in Nuke 12.0, and support for Nuke 12.0 is official!
Details:
The one issue found in Nuke 12.0 was a crash bug caused by how we applied styling to panel apps. This caused stability issues for Nuke when showing the shotgunpanel app under certain circumstances. That stability issue has been resolved in this release.
2019-Nov-01
Better management of sys.path during engine initialization.
Details:
Resolves an issue that caused the last path appended to sys.path during engine initialization to be removed from sys.path once bootstrapping completed. Also removes a redundant addition of the engine's python module to sys.path.
2019-Sept-30
Fixes a bug with the plugin based startup.
Details:
Fixes a bug with the plugin based startup, where if you had automatic context switching enabled and you opened a script via the Nuke menu when a script was already open, it would cause a new Nuke instance to start. On the startup of this second Nuke instance the engine would error.
2019-Jul-29
Fixes an issue introduced in v0.12.0 where Nuke freezes on startup when launched through Shotgun on Windows.
2019-Jul-11
Improved logging around context switching.
2019-Apr-15
Context change improvements.
Details:
-
The automatic context switching callbacks are no longer initialized outside of the main engine code. This means you can now bootstrap the nuke engine without having to initialize the callbacks separately.
-
The automatic context switching now uses the
engine.context_changemethod to switch contexts when an instantiated engine is available. This means that the panel app will update its context for example when a user opens or saves a file through Nuke's open menu. -
The engine now respects that different config environments might have different states of true or false for automatic context switching. In other words, you can go from an environment with it set to True to an environment with it set to False or vice versa, and it will behave accordingly.
-
Standardized the startup and automatic context switching so that they follow the same path regardless of if you are starting up for the first time or spawning a new Nuke instance with automatic context changing.
2019-Jan-14
Updates Nuke version to support 11.3
2018-Aug-06
added ability to set hotkeys in the tk-nuke.yml settings file
2018-Jul-25
Updates Nuke version to support 11.2
2018-Jul-09
Context changing now works correctly in non-ui mode.
2018-Jun-19
Updates logic around parsing Flame openclip files during publish.
Details:
We now use more reliable means of finding the first video track in an openclip file produced by Flame. We also preserve the openclip version number during our update of its contents.
2018-May-11
Properly handles "node" type engine commands in Nuke Studio when building menus.
Details:
This allows us to have something like tk-nuke-quickdailies configured for Nuke Studio without having it show up in the Shotgun menu on the main menu bar. Instead, we now separate out those engine commands and add them to the nodes menu, just like would be the case in Nuke.
2018-May-11
When publishing it now ensures that the work folder exists before attempting to save the script/project, in both Nuke and Nuke Studio.
2018-May-04
Updates Flame icon to the 2019 version.
2018-May-03
Fixed a bug with the publish description for "Submit for Review" plugin. It should now display the correct description, and not cause an error.
2018-Apr-16
No longer imports the QWebEngineWidgets submodule from PySide2 on Windows in Nuke 11+.
Details:
Importing QtWebEngineWidgets from PySide2 on Windows can cause an unrecoverable deadlock in some cases. Since we do not make use of it in any of the out-of-the-box Toolkit bundles or tk-core, we can safely skip importing that submodule. Any clients that require its use can import it directly from PySide2.
2018-Apr-12
Fixes engine initialization problems when running in Nuke 9.x.
2018-Feb-13
Supports updating of Flame OpenClip publishes when no templates are in use.
Details:
When no template exists to identify an OpenClip file for the current Shot, we attempt to find a published clip file that comes from the new-style Flame workflow that makes use of the publish2 app during sequence export. If a usable clip is found, we update its contents in the same way we've always done in template-driven workflows. This behavior drives the core of the Flame-to-Nuke workflow.
2017-Nov-15
Updates hook icons to match current version of Nuke
2017-Nov-15
Updated icons with proper gamma
2017-Nov-14
Adds support for review submission publish2 plugin
2017-Nov-08
Adds publish plugin for updating Flame clip files
2017-Nov-08
Now houses publish2 plugin hooks and supports template-based worklfows
2017-Aug-23
Fixes a regression related to File->New and File->Open operations.
Details:
Fixes introduced for Nuke 11.x compatibility caused a regression that resulted in a failure to properly initialize SGTK when a File->New or File->Open operation was performed from an already running session of Nuke.
2017-Aug-17
Fixes yet another crash-on-close bug in Nuke 11 on Linux.
2017-Aug-15
Fixes a crash on close in Nuke 11 on Linux.
2017-Aug-09
Fixes a crash on close in Nuke 11.
2017-Aug-08
Fixes for menu callbacks in Nuke 11 that caused errors when launching Toolkit apps.
2017-Aug-08
Compatibility with Nuke 11.0v1.
2017-Aug-07
Fixed a regression in v0.7.0 where pre-existing NUKE_PATH and HIERO_PLUGIN_PATH paths were not respected. The engine would wipe the environment variable paths and add it own custom ones, causing custom init.py and menu.py files not to be run. It now appends the custom toolkit paths to the end of the existing paths.
2017-Jun-29
Minor adjustments to logging output
2017-Jun-29
Minor adjustments to logging output
2017-May-03
Plugin support, Software discovery, 0.18 logging and settings for launching at startup.
2017-Apr-06
Fixes a bug in Hiero usage reporting.
2017-Feb-15
Updated Nuke version to support 10.5
2016-Nov-08
Adds custom equality logic for the Nuke panel wrapper class.
2016-Nov-03
Wrapped toolkit panel widgets are now accessible via their parent NukePanel objects.
2016-Aug-09
Allows node menu commands to be context specific.
2016-Aug-03
Switches to using onScriptLoad rather than onCreate to handle context setting.
Details:
This change is more efficient than the previous approach, and works around a Nuke bug that causes some node references in Python to not be properly attached to a back-end PythonObject under certain circumstances on some platforms.
2016-Jul-28
Fixes a regression in the bootstrap process for Nuke that caused tk_nuke_qt to be inaccessible.
2016-Jun-17
Only Disabling Parenting for Nuke 7
2016-Jun-15
Changes a log_warning to a log_debug to reduce noisy output.
Details:
This is going to be triggered on most launches of Hiero and Nuke Studio, as both will cause a file read of a template file that is unlikely to be stored in an SGTK-aware location. We don't need to be scaring the user with nasty output containing Python tracebacks when it's completely harmless.
2016-Jun-14
Adds an event callback for Hiero and Nuke Studio that will change Toolkit's context when opening a project file from File->Open and File->Recent Files if it is different from the current context.
2016-Jun-10
Skips triggering a context change if the new context is the same as the current context.
2016-Jun-09
Panel apps launch as dialogs when running in Hiero mode.
Details:
Hiero doesn't support embedding panels into its main window the way that Nuke and Nuke Studio do. As such, we redirect panel requests to show as dialogs to remain compatible.
2016-May-11
Tweaks for Nuke/Hiero/Nuke Studio 10.0v1 compatibility.
2016-Mar-29
Provides bootstrapping as part of Nuke's standard init.py startup.
Details:
Previously, we only bootstrapped and initialized Toolkit from a menu.py file. This menu.py is only sourced on launch when Nuke is running a GUI session, and as a result, running "nuke -t" did not initialize toolkit. We now have the same bootstrapping routine running from an init.py when Nuke is starting in batch mode.
2016-Feb-29
Ensures that we only call clearMenu on nuke.Menu objects.
2016-Feb-18
Adds a call to log a user metric for the DCC version
Requires tk-core version 0.17.0 or later.
Details:
The context-changing behavior of tk-nuke requires functionality provided in v0.17.0 or newer of tk-core.
Updated icons and bug fix for context changing.
Cleans up context behavior when changing tabs in an empty Nuke Studio session.
Adds full Nuke Studio integration.
Details:
Nuke Studio is now fully supported! When opening or focusing into a Nuke script within a Nuke Studio project, Toolkit will change to that context on the fly.
Adds Hiero 9.0 support.
Details:
Hiero 9.0 support has been added to the Nuke engine. This allows for a single engine to be used for multiple modes of Nuke. Also, until full Nuke Studio support is added, the engine will treat it as if it were Hiero, allowing Hiero menus and apps to be used from Nuke Studio. Instructions on how to upgrade to using the new tk-nuke engine with Hiero 9.0, please see this knowledge base article.
2015-Sep-18
Fixed an issue causing user login credentials not to be carried over on file open and file.
2015-Sep-18
Fixed a bug causing QT import errors when files were loaded via the file manager.
Adds panel support and new icons.
Details:
This implements the panel interfaces added in Core v0.16.15, allowing apps to dock panels into Nukes user interface. Panels can be saved to persist across sessions and launch at startup. This change also switches icons from the old T logo to the SG logo.
Nuke 9 is now officially supported.
Offical support for Nuke v8.0
Details: Default compatibility warnings have been bumped to any version of Nuke later than v8.0.x.
Added setting to customize name of the "Shotgun Current Project" favourite directory entry in the file chooser.
Details: You may also disable it by assigning an empty value to this setting.
Removed deprecated queue interface.
Details: This update removes the queue interface which was deprecated in Jaunary 2013. If any of the apps you use are still relying on these interfaces, please do not go ahead with this update but instead email us on toolkitsupport@shotgunsoftware.com.
Added a setting to control the compatibility warning dialog that gets shown for untested versions of Nuke.
Details:
- The
compatibility_dialog_min_versionsetting allows you to set the minimum major version of Nuke that the dialog will get displayed for. - If you need to disable the warning dialog for an untested version of Nuke, it is recommended that you set this to the next major version (e.g. 9 if you are using Nuke 8.0v4).
Fixed an issue with the error reporting which would cause it to fail when in non-ui mode.
add setting to add favorites to the file chooser
Details: Setting allows adding favorites to the file chooser. Thanks to @tokejepson for the pull request!
Errors emitted via the log_error() method are no longer shown via UI popups but just registered with the error log.
Fixes crash on exit in Nuke 7
Details: Remove main window parenting for Nuke 7 to avoid a crash on exit where the PySide Shiboken cleanup is happening after the python interpreter has been shut down.
Minor adjustments to how the menu items are sorted.
Fixed a bug in the menu generation which would cause Nuke 7.x to crash on Linux when the engine was destroyed.
Added a version warning for currently unsupported versions of Nuke to the engine startup
Renames and support for the new name Sgtk.
Renames and support for the new name Sgtk.
Better bookmarks handling.
Uses new API methods for file system access.
Updated icon and manifest.
Fixed a number of bugs
Details:
- Fixed issued with gizmo UNC paths on windows
- Fixed issues with the queue API being unstable
- Deprecated the queue API as part of v0.12.5 compliance
- added a has_ui property that reports when Nuke is running in batch mode
Misc bug fixes
Misc bug fixes.
UI tweaks and bug fixes.
- Widget library is now pyside/pyqt4 agnostic
- Added icon support for all nuke menu items.
- Tweaks to menu handling.
Bug fixes.
- Fixed a bug where multi selection would fail when item was substracted from the selected set.
- Better handling of window destruction in pyside
New UI and improved menu layouts.
(Requires Tank v0.10.8)
- New context UI with information about apps and environments.
- Improved menu with an option to add favourites.
The nuke engine now works with project only contexts.
First Release with the new Tank API.
Minor bug fixes.
- Fixed a bug which prevented the menu in Nuke from rendering correctly if the Core API returned unicode strings rather than std python strings.
Initial release to the App Store.