-
Notifications
You must be signed in to change notification settings - Fork 12
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-Oct-15
Improve multi-version support for user creation
2024-Sep-10
New Build resources
2024-Sep-10
New Build resources
2024-Sep-05
Fix Flame 2025.1 project creation
2024-Mar-26
Rebranding component for Flow Production Tracking
2024-Feb-28
Improve project creation and application startup
2023-Nov-23
Add support for QT6/PySide6
Details:
Add support for QT6/PySide6
2023-Apr-13
Update engine for start frame support
2022-Sep-26
Fix error closing QT windows
2022-Sep-07
Fix selection of proper application path for version extraction
2022-May-09
Fix issue with detecting application in SG desktop with Python 3
2022-Mar-28
ShotGrid branding updates.
2021-Dec-7
Fix selection of proper application path for version extraction.
2021-Nov-30
Replacing shotgunsoftware urls with Autodesk Knowledge Network and ShotGrid Developer Documentation pages.
2021-Jul-28
Improve command line handling
2021-Jun-17
Improve support for machine having FQDN in host name
2021-Jun-15
Shotgun to ShotGrid
2021-Jun-10
Shotgun to ShotGrid
2021-Mar-19
Enable shotgun command line jobs in backburner if available
2021-Feb-26
Use default command job by default
2021-Feb-23
Update to python 3
2020-Mar-19
Add an env var to set the Backburner Shared tmp
2019-Oct-30
Use Flame python for thumbnail upload
2019-Oct-07
Fix sending backburner job on fully qualified host name
Details:
Fix sending backburner job on fully qualified host name
2019-Jun-17
Fix assetType not correctly defined when rendering in batch
2019-May-29
Improve backburner job name sanitization
2019-May-15
Support more asset types in publisher
2019-Apr-29
Support more asset types in publisher
2019-Apr-10
Automatic job delete on completion / Burn publish workflow fix
2019-Feb-27
Do not use multiple server if shared backburner tmp is /tmp
2018-Nov-20
Support absolute paths to Open Clip when creating batch group
2018-Oct-09
Misc Fixes
2018-Oct-01
Improve zero-config create batch workflow
2018-Sep-14
2018-Sep-07
Support creating transcoding job of unwritten quicktime file
2018-Sep-07
Support creating transcoding job of unwritten quicktime file
2018-Aug-08
Fix import of Wiretap Python API from adsk site-packages
2018-Aug-01
Flame 2019.1 Integration
2018-Jun-28
Do not show Load in new Batch Group option if no batch file present
2018-Jun-18
Fix single frame render
2018-Jun-07
Support write file node render without shot entity / Upgrade minimum tk-core
2018-Jun-05
Upgrade tk-core / Support write file node render without shot entity
2018-May-17
Support for QT 5.9 / Support for Movie Assets
2018-Apr-26
Upgraded to Flame 2019 icons.
2018-Apr-11
Use the sequence drop flag instead of the source one for the cut
2018-Mar-06
Treats OS X the same as Linux for Software launcher paths.
Details:
We now launch all Flame family products from the startApplication executable, regardless of whether we're on Linux or OS X. This resolves a launcher problem on OS X from a classic config, which would bail out with path parsing problems, and then also wouldn't be able to find the bundled python executable.
2018-Feb-28
Multiple small ajusments
Details:
Multiple small ajusments
2018-Feb-12
Multiple small fixes.
Details:
Multiple small fixes.
2018-Jan-19
2018-Dec-06
Fixes for how classic sgtk integration Flame projects are treated when launching Flame using the bundled sgtk plugin-based integration.
Details:
- Only warns the user if crossing SG project bounds on Flame project switch.
- When launching in classic mode, we link the flame and sg projects in the same way that the Flame sgtk plugin does. This means that Classic toolkit projects won't trigger Flame's project connect dialog to pop up when loaded from a standalone (not launched from SG Desktop) Flame launch.
2017-Nov-08
tk-multi-publish2/tk-multi-loader2 hooks implementation
2017-Nov-08
tk-multi-publish2/tk-multi-loader2 hooks implementation
2017-Nov-08
2017-Nov-08
tk-multi-publish2/tk-multi-loader2 hooks implementation
2017-Oct-24
Adds legacy/classic startup logic for Software launchers.
2017-Oct-10
Add a possibility to specify the backburner servers/group used on job submission
2017-Sep-28
Bug fix: Unregister tk-flame hooks on engine destruction
2017-Sep-28
Add a possibility to specify the backburner servers/group used on job submission
Details:
New tk-flame configuration entry available: backburner_servers and backburner_server_group.
2017-Sep-14
Fix Flame executable detection on Mac OS
2017-Aug-28
Add launch context to the FlameLauncher
2017-Jun-22
Better error handling on log file
2017-Jun-09
Improve Version Checking
2017-Jun-07
Adds software scan support for mac update releases. Fixes logging permissions issues.
2017-Jun-05
Adds automatic software scanning logic and interfaces.
2017-Apr-06
Fix Shot Export on Mac and RHEL6 for flame 2016 and 2017
2017-Apr-05
Fix Shotgun Shot Export for flame 2016.1 to 2017.2
2017-Apr-04
Added menu ordering in the shotgun main menu
2017-Mar-30
Added setup directory and group selection in project creation UI.
2017-Jan-23
Fix python hook crash when user implement their own version of the preCustomExport python hook.
2017-Jan-23
Support remote Backburner Manager when submitting clip to review with toolkit as a plugin.
2017-Jan-04
Ensures that Backburner reads Toolkit settings and writes logs in the home folder.
2016-Dec-19
A series of tweaks and fixes to allow the flame engine to be packaged in a plugin.
2016-Nov-03
Updated Flame icons and adding validation to see if Shotgun is disabled
2016-Oct-26
Renamed some of the hook files for better compatibility when running shotgun alongside other integrations.
2016-Aug-11
Registered commands now automatically appear on the menu.
2016-Jul-15
Added support for 2016 export preset paths.
2016-Jul-12
Added export_presets_root convenience property.
2016-Jul-11
Added support for non-launchapp init of the engine.
2016-Jul-10
Engine now reports upgraded export presets for Flame 2017.
2016-Jun-13
Updated to support more flexible install paths
2016-Apr-25
Compatibility adjustments to Flame 2017 preset logic.
2016-Apr-18
Now supports profile presets for Flame 2017. Increased backburner timeout to 600 minutes.
2016-Feb-24
moved version logging to engine post app init
2016-Feb-18
Adds a call to log a user metric for the DCC version
2015-Nov-18
Support for proxy settings introduced in Flame 2016 Extension 1. Ability to run flame batch from a shot.
2015-Oct-08
Added support for exposing Toolkit commands via the Flame context menu.
2015-Oct-06
Flame user names are now based on the full flame version number.
2015-Oct-05
Updated to support Flame 2016 Extension 1
Details:
- Updated flame export preset version to 6 for 2016.1 and above
- Added support for a backburner manager parameter for 2016.1 and above. Adds a new parameter to the engine configuration which means the the Shotgun/Flame integration now supports remote render farms. This change required some internal bug fixes in Flame, so the new config option will be ignored on versions prior to 2016.1
2015-Sep-08
Add ability to run configured apps on Flame launch
Fixed a Flame issue when having a space in the Pipeline Configuration and Primary paths
Minor polish and improvements.
Details:
Improved logging, documentation and general code structure.
Improved error logging.
Fixed an issue causing project creation to fail in Flame v2015.2
Improved default creation of user names.
Details:
The hook that generates user names has been improved to include the major version of Flame. This is to ensure that the Shotgun integration can gracefully handle switches between major versions in flame, since user accounts can be incompatible between releases.
Added support for visual depth in the project settings hook. Defaults to 16 bit.
FPS Support and compatibility changes.
Details:
- Frame rate (FPS) is now supported by the project UI and project setup hook.
- Removed a method which was returning misleading frame defaults.
- Added a method to detect which xml preset version that the DCC expects.
Note! This release changes the behaviour around how in/out frame numbers are normalized prior to being
pushed to shotgun. Previously, the integration tried to normalize frame values in Flame that had been offset by an internal flame setting (usually set to 10:00:00.00) but this is no longer the case. Instead, the values in Shotgun will appear exactly the way they appear in the conform view in Flame.
The Shotgun Flame integration updated for Flame compatibility.
- Improved python detection for backburner jobs
- Improved support for detection of flame version numbers
Improved support for partial flame version numbers.
Added additional checks to make sure the executable exists.
Updated Flame compatibility.
Fixed a bug which caused backburner jobs to fail for sequences with very long names.
Misc minor adjustments and fixes.
- Fixed an issue causing Flame to fail to launch on linux if a system install of PySide was present.
- Added logging to file and improved exception handling in UIs showing up outside Flame.
- Added the ability to choose volume interactively at project setup.
- Added better version checks at startup to ensure a minimum version (2015.2) of Flame is being used.
UI Polish and tweaks.
First official release of the Shotgun Flame integration.