Visit the Release Mailer Signup page on the Deadline website to get notified of Deadline releases.


Deadline 10.1 reflects our ongoing investment in performance and scale with worker count now scaling up to 10x more instances on Linux and up to 4x more instances on Windows operating systems [1] compared to previous Deadline releases, providing the ability to scale bigger and faster than ever to complete your projects.

This release adds more support for popular content production tools. SideFX Houdini can now be used in AWS Portal, and usage based licensing (UBL) for SideFX Houdini Engine is now available on the AWS Thinkbox Marketplace (Mantra support to follow in an upcoming release). Foundry Modo 13 is now supported in Deadline with updated submitter functionality. There are also a number of updates to plugins for your favorite tools, including Autodesk Maya, OTOY Octane, Maxon Cinema 4D, Foundry Nuke, Ftrack, and many others.

We’ve made it easier to use Deadline on AWS. While it’s always been that case that when you pay for the AWS resources that you use for rendering (EC2 instances, EFS storage, and so forth) you could use Deadline at no charge, it required a few extra steps to get credit. With Deadline 10.1, a new improved billing process provides AWS Thinkbox Deadline customers with a more streamlined experience by removing the upfront payment requirement. Additionally, Deadline can now automatically detect if it is running on AWS and will no longer require any licensing setup of any kind.

Finally, Deadline has now completely removed Mono as a dependency, leveraging .NET Core for MacOS, Windows, and Linux. This change allows us to standardize on a single framework, enabling more frequent updates for Deadline with the latest performance and security improvements.

With the launch of Deadline 10.1, the following operating systems are no longer supported: Windows Vista, Ubuntu 12.04 - 13.10, Debian 7, Fedora 16 - 23, and macOS: 10.9 - 10.11. In addition, support for the deprecated Quicktime Standalone plugin has been removed completely, and the ability to disable the Sandbox process for Application and Event plugins has also been removed.


If you are using Deadline floating licenses, a new 10.1 license is required to run this version. If you have floating licenses for Deadline 10.0 or earlier, you will need an updated license. If you are using usage based licensing (UBL), any existing Deadline render time can be used with Deadline 10.1. If you are running Deadline 10.1 on AWS, no Deadline licensing of any kind is required.

Upgrading to Deadline 10.1

If you are upgrading from Deadline 9 or earlier, you will need to perform a fresh installation of the Deadline Repository and Clients.

If you are upgrading from Deadline 10.0, there are important things to note:

  • Auto-upgrading from Deadline 10.0 to 10.1 is supported, but auto-downgrading from 10.1 to 10.0 is not, unless 10.0 was previously installed on the machine.
  • If you are using the Remote Connection Server (RCS), you need to upgrade the RCS to 10.1 before upgrading all other Deadline Client installations to 10.1. This ensures that the Clients can communicate properly with the RCS, because a 10.0 Client cannot communicate with a 10.1 RCS.
  • If you are using a TLS-enabled Remote Connection Server (RCS), note that a 10.0 Client will not be able to communicate with a future 10.1.1 RCS. To upgrade from 10.0 to 10.1.1 and later, you will need to upgrade to 10.1 first, and then upgrade again to the latest 10.1.X version.
  • If you are using AWS Portal, you need to upgrade every AWS Portal component. This includes the Deadline Client on the machine connecting to AWS Portal, the AWS Portal Link service, any existing AWS Portal infrastructure and instances, and the IAM policy for your AWS Portal account.

Refer to the Deadline Auto-upgrading Documentation for more information.

Highlighted Features

Free Deadline Licensing on AWS

Licensing for Deadline 10.1 is now free when being run on AWS. The Deadline Worker no longer requires a license (floating or usage based) when running on AWS instances. If you already have floating or usage based licensing for Deadline, the Worker will not consume them when running on AWS instances. Note that Deadline 10.0 and earlier still require a license to run on AWS instances.

Improved Remote Connection Server (RCS) Performance and security

The RCS can now support thousands of Worker instances communicating with it concurrently, making the RCS the recommended configuration when setting up your render farm. This allows you to scale your on-premise, Cloud, or hybrid render farm to even larger concurrent Worker counts.

In addition, the RCS now supports TLS 1.2. Note that if you are upgrading from Deadline 10.0, and you’re using a TLS-enabled RCS, there are specific instructions for upgrading that you need to follow. See the “Upgrading to Deadline 10.1” section above for more information.

New Product and workflow Support

Houdini can now be used in AWS Portal, and usage based licensing (UBL) for Houdini Engine is now available on the AWS Thinkbox Marketplace (note that Mantra support is not yet available, we are working on including Mantra at a later date).

This release also adds support for Modo 13, and adds support for the Octane ORBX export workflow to Cinema 4D.

Scripting API Code Completion

Support for Python code completion for Deadline’s Python API has been added. The “deadline-stubs” Python package can be installed for VS Code or PyCharm to add code completion support and allow you to browse the available classes and functions. Refer to the Scripting Overview section of the Deadline documentation for more information.

Introducing the Deadline Worker

The Deadline Worker is the new name for the previous Deadline Slave application. The name is the only thing that has changed, and there is no difference in functionality between the two applications.

Upgrade to .NET Core

The Deadline Client applications now run with .NET Core on all operating systems. This change allows us to standardize on a single Framework, and stay up to date on the latest performance and security improvements going forward.

Complete Release Notes

General Improvements

  • The Deadline Client applications now run with .NET Core on all operating systems.
  • The Deadline Client and Repository installers can now run on macOS Catalina.
  • Fixed some issues with how Path Mapping was being applied to a Job’s Custom Plugin Directory path.
  • Fixed an issue with Job failure detection, where it wouldn’t respect Job-specific overrides in some cases.
  • Updated Splash Screens and icons.

AWS Portal Improvements

  • When selecting instance types, the Monitor only displays the types available in the selected Availability Zones. This ensures that the instance type is actually available in the Zones that are selected.
  • AWS Portal now supports TLS connections to an on-premise Remote Connection Server (RCS).
  • Fixed an error that would occur when creating the S3 bucket in us-east-1 during AWS Portal setup.
  • More descriptive information is now provided when the Monitor cannot connect to the AWS Portal infrastructure.
  • Fixed a typo in an error message for the Resource Tracker.
  • AMIs are now based on Amazon Linux 2 instead of Amazon Linux 1.

Monitor Improvements

  • The Worker panel in the Monitor now includes columns for AWS Image ID, Instance Type, and Availability Zone.

Worker Improvements

  • The Worker application no longer requires a Deadline license (floating or usage based) when running on an AWS instance. Note that this only applies to version 10.1 of the Worker application and later.
  • When applying the environment variables for a Job on Windows, the Worker no longer throws an error if there are 2 environment variables with the same name, but have a different mix of uppercase and lowercase letters. Now, only the last of the duplicated environment variables in the list is applied.
  • When the Worker fails to connect to a Repository, the Exit Worker option now actually shuts down the Worker.

Remote Connection Server (RCS) Improvements

  • The RCS now supports TLS 1.2. TLS 1.0 and 1.1 are still supported in Deadline 10.1 to accommodate auto-upgrading from 10.0, but TLS 1.0 & 1.1 will be removed in the next Deadline 10.1 release.
  • Significantly improved the performance of the RCS as the number of Worker nodes increases.

Scripting Improvements

  • Added support for Python code completion for VS Code and PyCharm.

Application Plugin Improvements

3ds Max

  • Fixed an issue when submitting Tile/Jigsaw jobs that could prevent Deadline from collecting external files.

Anime Studio / Moho

  • Fixed a bug that prevented the Monitor submission script from working.

Cinema 4D

  • Added support for the Octane ORBX scene export workflow to the integrated submitter.
  • Fixed a submission error that occurred when submitting Multipass objects from non-English versions of Cinema 4D.


  • Tile Assembly jobs can now handle config files that contain empty spaces around the ‘=’ character.


  • Fixed a “KeyError” issue that could occur when using the integrated submitter.


  • Added support for Houdini licensing in the Thinkbox Marketplace.
  • Fixed an issue that could occur when rendering with Octane that would result in MPlay options not being set correctly.
  • When rendering with Octane, render progress is now reported properly.
  • When rendering with Redshift, Deadline now properly handles licensing error messages.


  • Keyshot Package (KSP) files can now be submitted to Deadline from the Monitor.


  • Deadline now catches the “Failed to save file” error message and reports it as an error.


  • Added support for Modo 13.


  • The integrated submitter no longer crashes when submitting Nuke scene files with Write nodes that have an empty path.


  • Added a popup handler for Flamingo nXt.

Event Plugin Improvements


  • Updated the version of the FTrack API that Deadline uses to 1.8.0.
  • Added support for encoding videos and images, allowing them to be reviewed in FTrack after rendering.

Spot Event Plugin

  • Non-existing Limits that are assigned to Jobs are now ignored.
  • The plugin now handles the case where the Resource Tracker is disabled after the Spot Event plugin is enabled.
  • The plugin now only starts up a single instance if a Job has a pre-task script. Once the pre-task script is completed, the plugin will then start up more instances as necessary.
  • Improved how the plugin handles instance interruption.


[1]Performance changes focused on improved API’s for dequeue operations and the collection of status information from workers. Resulting tests in simulated environments on Amazon Linux 2 and Windows Server 2016 where we scaled workers in batches of 800 at a time with a single server resulted in a 10x scale of infrastructure on Linux and over 4x on Windows platforms vs. Deadline