-
Notifications
You must be signed in to change notification settings - Fork 40
Release Notes
Welcome to the release notes for this 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!
2021-Dec-1
Replacing shotgunsoftware urls with Autodesk Knowledge Network and ShotGrid Developer Documentation pages.
2021-Jun-10
Rebranded to ShotGrid
2021-Mar-23
Python 3 compatibility.
2019-Apr-15
Fixes an issue so that when the context changes due to the engine's file automatic context switching, the path and profiles get correctly updated on the SG writenodes in the newly opened script.
2018-Sep-14
A cleaning up of code in relation to the convert menu item feature added previously.
2018-Sep-14
Adds a new configurable option that exposes the API's convert methods as UI actions in the Shotgun Menu.
Details:
- Adds two new actions under the Shotgun menu that enable converting to and from Shotgun write nodes. These options can be enabled by setting the app setting
show_convert_actions: True. However, they won't be shown if you are using promoted knobs in any of the Shotgun write node presets. - Shotgun write nodes converted to standard Nuke write nodes will now have the "create directories" option ticked on.
2018-Jun-04
Addresses problems that arise from opening files in Nuke via the "recent files" menu option, plus a promoted write knobs fix.
Details:
When opening files from the "recent files" menu in Nuke, if the writenode app isn't configured in the current environment, the app would fail to properly set profiles on the gizmos on read. In addition, a flaw in the logic related to initializing promoted write knob values on launch was discovered and fixed.
2018-Jan-19
Reverts a portion of the v1.3.0 release related to resolving a ValueError raised by Nuke in some situation on file open.
Details:
The portion of the 1.3.0 release that resolved a PythonObject ValueError from Nuke in some situation on file read has been reverted. The change required to fix that issue had unforeseen consequences for some clients when rendering in a farm context.
2018-Jan-15
Fixes preservation of promoted knob settings between sessions, and adds a new public method to the API.
Details:
- Promoted write knobs maintain their settings across Nuke sessions.
- Addressing the "a pythonObject is not attached to a node" ValueError exception using a generator.
- Adds a new public method to the API for creating node instances programmatically.
Adds a Python tab that's the equivalent of the encapsulated Write node's.
Re-caches the work file template on context change.
Resolves bug related to node profile refreshing during context change. This resulted in the profile menu items in Nuke not being properly rebuilt.
Fixes render path regression. Handles menu rebuilding on context change.
Resolves a ValueError raised by Nuke's colorspaces.py module in Nuke 10.0.
Details:
Recomputing the render paths after restoring cached knob settings caused the exception to be raised. Rather than recompute the paths, we're now removing the the file and proxy knob settings from the cache before applying it. This means we don't need to do the recompute and therefore we no longer see the error.
Updates output name during paste operations.
Details:
When copy/pasting a node that has the "use node name" option checked on to force the output name to match the node name, the output name will now be updated to match the new name of the pasted node.
Resolves regression related to file and proxy paths.
Details:
The file and proxy paths of the encapsulated write node lost their connections to the top-level Gizmo's cached paths. This resulted in paths with baked-in frame numbers instead of typical %04d tokens.
Adds support for Nuke Studio context changes.
Bug fix for promoted write nobs not retaining their user-set values after relaunch.
Details:
Promoted write knobs would revert to their preset's default value for that knob when the file was reloaded. These knobs will now be treated as other top-level tk-nuke-writenode knobs that are user controlled such that the user-set values are no longer lost.
Allows the promotion of write-node knobs to the gizmo's UI.
Details:
Exposes a new profile config option "promote_write_knobs", which can take a list of knob names to promote from the gizmo's internal write node up to the top-level user interface. These knobs can be file-type specific knobs as long as the knobs promoted come from the file type utilized by the profile.
Allows the promotion of write-node knobs to the gizmo's UI.
Details:
Exposes a new profile config option "promote_write_knobs", which can take a list of knob names to promote from the gizmo's internal write node up to the top-level user interface. These knobs can be file-type specific knobs as long as the knobs promoted come from the file type utilized by the profile.
Allows the promotion of write-node knobs to the gizmo's UI.
Details:
Exposes a new profile config option "promote_write_knobs", which can take a list of knob names to promote from the gizmo's internal write node up to the top-level user interface. These knobs can be file-type specific knobs as long as the knobs promoted come from the file type utilized by the profile.
Stopped un-handled exception from being raised when computing the render path in an un-saved script
Fix for incorrect proxy path setting when converting to Write nodes
Details:
If no render_proxy_template is specified in the settings, this fix ensures that when converting to Nuke Write nodes, the proxy value is empty. Previously it was being set to the render_template path.
Bug fixes
Details:
- Fixed problem where the conversion from Nuke write nodes back to Shotgun write nodes wasn't updating the profile drop-down menu correctly. This made it look like the wrong profile was being used.
- Fixed an issue that stopped the 'Reset Path' button and warning being visible when the render path no longer matches the cached render path! This made it difficult to reset the render path if for some reason it had become locked.
Fixed render path update when it contains width or height.
Details
- There was a bug that was stopping the render path from updating the width and height keys when the render size was changed for a script. This has now been fixed.
Fixed various initialisation issues.
Details
- Found and fixed a few edge cases that would throw 'PythonObject is not attached to a node' errors in Nuke, resulting in the app not being loaded and the script being left in an error'd state.
Top level knobs/settings are no longer reset on file open!
Details:
- Previously specifying a setting for a profile that is represented by a top-level knob on the Shotgun Write node would result in that knob being reset every time the script is loaded. This has bnow been fixed so that the knob will only get set at node creation or when the profile on the node is changed.
add date fields YYYY, DD, MM for use in render path templates
Details:
allows users to use the template fields YYYY, MM, DD in their render path template. These fields will be ignored in the validation that checks to see if the render path has changed since date fields kind of imply that the path will change.
File type & settings are now retained after node creation
Details: Previously this information would be lost after the script was first saved and never re-populated from the profile in the environment. This is now fixed so that the file type and settings are always updated to match the current profile!
User experience improvements
Details:
- Removed the 'Shotgun Write' prefix for the node creation commands to make it easier to create nodes from the tab shortcut menu
- Added a tile_color setting to the profile which can be used to set the background colour in the node graph for a node based on the profile
Renamed 'channel' to 'output' as channel conflicts with other Nuke terminology
Details:
- The channel key in templates is still supported for backwards compatibility but the new 'output' key can now be used instead.
- The behaviour remains unchanged.
Added debug functions to the app to forcibly enable/disable path evaluation.
Performance improvements during rendering and playback
Fixed issue when rendering in proxy mode
Updated to require core v0.14.37
Fixed issue when rendering in proxy mode
Numerous changes, improvements and fixes
Details:
- Added ability to switch between profiles without having to delete/recreate the node
- New conversion methods on the app to convert to/from regular Nuke Write nodes
- Added support for separate proxy render & publish templates
- Addition of copy-path button
- Improvements to the behaviour of the channel knob including addition of the option to drive it from the node name
- Nuke scripts are no longer left in a modified state immediately after opening
- Fixed issues with threading evaluation during rendering that could cause frames not to render
- Added missing knobs from regular Write nodes (e.g. Reading)
- Removed the counter-intuitive auto-node-naming feature - new Shotgun Write nodes are now just named ShotgunWrite#
- Disabling a Shotgun Write node now behaves as expected
- Fixed issues stopping cacheing from working effectively in Nuke 7+
- Relaxed template field requirements to allow additional fields to be used from the work file template in the render path
- Improved warning messages/handling when something is wrong
Added support for ShotgunWriteNodePlaceholder
Details: Any ShotgunWriteNodePlaceholders will be converted to Shotgun Write Nodes using the config setting for passed in name and channel name.
Channel knob is now hidden if the render template doesn't contain a channel key
Spaces in Shotgun Write Node names are now replaced with underscores to conform to the Nuke standard
Removed unnecessary template validation from app that was forcing 'name' to be required in the render and publish templates
Fixed a bug preventing the jump to file system to work with UNC paths on Windows.
Addition of get_node_published_file_type method to app
Renames and support for the new name Sgtk.
- Tank Write Nodes now use the current render & publish templates specified in the configuration. Previously they were using the templates specified when the node was first created.
- The local node render resolution is now used when constructing the render path rather than the global resolution.
Added interface to app to check if a write node's render path is currently locked
First release to the Tank Store.