Nuke Connect Plugin Install - HOW?!?!??!?!
1 1

12 posts in this topic

I'm getting quite fed up with the old or lack of manuals about the setup of ftrack and the connect plugins.

I've got as far as adding some of the Environement variables and finding the ftrack connect plugin folder.

Now when loading Nuke (not from ftrack, our Nuke is based on a networkshare and therefore I guess, not found by the launcher) I get the following errors:


Can anybody point me in the right direction?


OS: Windows 10 / Server 2012 network / Nuke 10 / Adobe Creative Cloud / Maya / Unreal





Share this post

Link to post
Share on other sites
1 hour ago, RicardoMusch said:

No, our Nuke is installed on a network share and therefore connect doesn't find it automatically.

It seems that the problem is that the nuke plugin does not have all it's dependencies available on the PYTHONPATH. There are quite a lot of dependencies so it can be a bit tricky to get it right. And I agree with you, this should be easier and covered much better in the documentation.

So I guess there are two ways to do it then:

1. Using connect package: You add a custom launcher as a Connect plugin that can scan and find Nuke on your network share. This has the advantage that you can reference the existing launch hook and utilise the way it makes the dependencies available.

2. Standalone: You make the necessary dependencies available: . Note that e.g. ftrack-connect has dependencies as well so there are quite a lot.

Share this post

Link to post
Share on other sites
4 minutes ago, RicardoMusch said:

So I installed Nuke Locally, it's now in the launcher.

But now it's erroring when interpreting the


So for clarity: Where does the PYTHONPATH variable need to point to exactly?


Just so that I understand you correctly, you have:

1. Installed nuke locally

2. Downloaded and running Connect package

3. Launching nuke through Connect package

If above is correct you should not have to set the PYTHONPATH or anything. Is that the steps you took and you get this issue? If so I will ask one of the devs to jump in and see if we can debug this.


Wouldn't it be much better to be able to specify commands available in the launcher via the Ftrack interface Back-end?

It absolutely would, I will make sure we have a feature request ticket to cover this!

Share this post

Link to post
Share on other sites

Hi there,

I am having a similar problem while manually installing connector for nuke. I have the following packages and their python dependencies: 

  • ftrack-connect-nuke
  • ftrack-connect-foundry
  • ftrack-connect
  • ftrack-python-api
  • ftrack-api

Everything is stored on the network using REZ to resolve dependencies and create env. I can correctly use ftrack-connect app, and both APIs but I fail to load the asset manager inside nuke

How should I alter NUKE_PATH,  PYTHONPATH and any other env vars to load the plugin corrrectly ?

At the moment I have the following NUKE_PATH:

  • /path/to/my/ftrack_connect_foundry/0.1.0/payload/build/lib/FnAssetAPI
  • /path/to/my/ftrack_connect_foundry/0.1.0/payload/build/lib/ftrack_connect_foundry
  • /path/to/my/ftrack_connect_foundry/0.1.0/payload/build/lib/assetmgr_nuke
  • /path/to/my/ftrack_connect_nuke/0.1.9/payload/build/lib/ftrack_connect_nuke



Share this post

Link to post
Share on other sites

Well I was missing the following value in NUKE_PATH: 


Now it seems to catch the plugin but fails with the following log:

Nuke 10.0v3, 64 bit, built Jun 27 2016.
Copyright (c) 2016 The Foundry Visionmongers Ltd.  All Rights Reserved.
Traceback (most recent call last):
  File "/.../ftrack_connect_nuke/0.1.9/payload/resource/nuke_path/", line 5, in <module>
    import ftrack_connect_nuke
  File "/.../ftrack_connect_nuke/0.1.9/payload/build/lib/ftrack_connect_nuke/", line 6, in <module>
    import ftrack_connect_nuke.plugin
  File "/.../ftrack_connect_nuke/0.1.9/payload/build/lib/ftrack_connect_nuke/", line 4, in <module>
    import ftrack_connect_foundry.plugin
  File "/.../ftrack_connect_foundry/0.1.0/payload/build/lib/ftrack_connect_foundry/", line 6, in <module>
    import ftrack_connect_foundry.bridge
  File "/.../ftrack_connect_foundry/0.1.0/payload/build/lib/ftrack_connect_foundry/", line 13, in <module>
    import ftrack
  File "/.../ftrack_api/3.3.30/python/", line 20, in <module>
    from FTrackCore import *
  File "/.../ftrack_api/3.3.30/python/FTrackCore.egg/FTrackCore/", line 10, in <module>
  File "/.../ftrack_api/3.3.30/python/FTrackCore.egg/FTrackCore/api/location/", line 3, in <module>
    from .Entity import Entity
  File "/.../ftrack_api/3.3.30/python/FTrackCore.egg/FTrackCore/api/location/", line 19, in <module>
  File "/.../ftrack_api/3.3.30/python/FTrackCore.egg/FTrackCore/api/event/", line 5, in <module>
    from .Host import Host
  File "/.../ftrack_api/3.3.30/python/FTrackCore.egg/FTrackCore/api/event/", line 18, in <module>
  File "/.../requests/2.3.0/requests-2.3.0-py2.6.egg/requests-2.3.0-py2.6.egg/requests/", line 53, in <module>
    from .packages.urllib3.contrib import pyopenssl
  File "/.../requests/2.3.0/requests-2.3.0-py2.6.egg/requests-2.3.0-py2.6.egg/requests/packages/", line 3, in <module>
    from . import urllib3
  File "/.../requests/2.3.0/requests-2.3.0-py2.6.egg/requests-2.3.0-py2.6.egg/requests/packages/urllib3/", line 16, in <module>
    from .connectionpool import (
  File "/.../requests/2.3.0/requests-2.3.0-py2.6.egg/requests-2.3.0-py2.6.egg/requests/packages/urllib3/", line 43, in <module>
    from .response import HTTPResponse
  File "/.../requests/2.3.0/requests-2.3.0-py2.6.egg/requests-2.3.0-py2.6.egg/requests/packages/urllib3/", line 18, in <module>
    log = logging.getLogger(__name__)
AttributeError: 'module' object has no attribute 'getLogger'


Share this post

Link to post
Share on other sites

Hi Jerome,

Here is a shell script that I sometime use for developing the ftrack-connect-nuke plugin. In this setup I'm running nuke from source, but loads the dependencies from the that is found the Connect package. If you do not want to do that, you can unpack to see the dependencies that it contains.

# Set path to the ftrack-connect-nuke repository.
export FTRACK_CONNECT_NUKE=/path/to/ftrack-connect-nuke-repository/

# Set nuke plugin path.
export NUKE_PATH=$FTRACK_CONNECT_NUKE/resource/nuke_path

# Set environments variables for foundry asset plugin.

# Set PYTHONPATH to ftrack-connect-nuke and shared libraries.
export PYTHONPATH=${PYTHONPATH}:/path/to/

# Set task and shot id.
export FTRACK_TASKID="task id"
export FTRACK_SHOTID="id of the parent to the task"

Let me know if this helps!

I'm running on OS X so the path to the for me is "/Applications/" but must be changed according to your OS.

Share this post

Link to post
Share on other sites

Hi Mattias,

Very helpful: I was missing the correct value for FOUNDRY_ASSET_PLUGIN_PATH

the packages from bitbucket donnot come with archive though so I did not have to update the PYTHONPATH.

I now have a proper ftrack_connect / nuke integration working but publishing seems to failed when creating a component to a custom location...

Thanks for your help !

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
1 1