Note: Nuke PLE is not supported.

The scene parser is not able to read the scene information as Nuke encodes the PLE files. 

"Shared Exe" installation

RR requires a local Nuke installation by default.

But it is possible to use Nuke with a "Shared Exe" application folder.

Please see file [RR]\render_apps\_config\additional\ for installation instructions.

 Interactive Licenses

If you want to use interactive licenses for Nuke, then you have two options:

  • RR license groups:
    Open rrConfig, tab "Per Client Config". 
    Select the client that should use a workstation license.
    Change the "Render License Group" to "Workstation".

    Note: If you want to disable this behavior, please edit the file RR\render_apps\_setenv\all\nuke__inhouse.rrEnv

  • Additional parameter:
    Open rrConfig, tab "Per Client Config".
    Select the client that should use a workstation license, open sub-tab Render applications.
    At the end of the line with Nuke, add the -i flag to the additional parameter setting.


If you have plugins you need to use with Nuke, then you can place them into the folder


(of course you have to change the os and nuke version in the path)

You can also place a file named in that folder.

Inside this python script, you can define plugin paths like (and print the path to check if everything is right):




nuke.tprint('OUR FARM ENV')




Please execute the rrWorkstationInstaller install the submission plugin.

In Nuke, you have to run the script as shown in the screenshot.

It will read all comp settings and send them to the rrSubmitter.

Note: You can also start the rrSubmitter manually and load (multiple) scene files.

BUT loading the comp file directly into the rrSubmtter can not evaluate scripted file names in your write nodes.


Local Render Out

With Local Render Out Nuke will write to the Local Data Folder.

So you do not have an enduring file connection to your fileserver. The output files are copied at once when they are finished.

To use Local Render Out with Nuke, you have to have Local Scene Copy as  well.

The rrClient runs a pre-script to replace all paths for read and write nodes (scripted filenames are resolved).

Then it saves the new nuke composite locally.

Render one view

If you want to render one view, then please enter --view myview to the Additional commandline flags at the rrSubmitter


License failure

The error looks like this:

License failure:

License server machine is down or not responding.

See the system adminstrator about starting the license server system, or

make sure you're referring to the right host (see LM_LICENSE_FILE).

Feature: nuke_r


License path: C:\ProgramData\The Foundry\FLEXlm\example.lic;C:\Program Files\The Foundry -


FLEXnet Licensing error:-96,7. System Error: 11004 "WinSock: Valid name, but no record (NO_ADDRESS)"

For further information, refer to the FLEXnet Licensing End User Guide,

available at "".

Solutions with an environment variable:

  • If you have defined the license location via the environment variable FOUNDRY_LICENSE_FILE on your work-/render-stations, then make sure you have set it as global system variable. (requires a system restart)
  • Otherwise, you can also edit the Setenv file for Nuke, remove the comment from the set variable FOUNDRY_LICENSE_FILE and place it there.

      (no restart required) 

Please refer to your Nuke documentation what you have to set as value for the env variable. 

3rd party

Shotgun write nodes

If you use Shotgun nodes, then you have to convert your Nuke files:

RR has prepared a render config for such comp files.

They will be converted at rendering.

You need to have Local Scene Copy enabled for the job.

And the shotgun toolkit (sgtk) module needs to be copied into [RR]/plugins/python_modules/