Search the Community
Showing results for tags 'environment'.
Hello all, My goal is to launch programs such as windows shell, Maya & Nuke, etc, from the ftrack UI and also feed custom environment variables to the shell before the application is launched. For example, I know project A requires Nuke 8.0 and Ocula 1.0 and project B requires Nuke 9.0 & Ocula 2.0 . I'm hoping to make/update a UI in ftrack which would have a Nuke icon and if the user double clicks the Nuke icon, the correct version of Nuke and plug-in are found via the environment variables. I can do this with other web based production tracking software and via a comman
Hi all, is there any reason why the Python paths from environment are not appended to the compiled ftrack_connect_package (v0.5.0) when is launched? If I create a simple action which print the sys.path I get this: .../ftrack/3.3.31/connect/0.5.0/centos-6_x86-64/common.zip .../ftrack/3.3.31/connect/0.5.0/centos-6_x86-64/ftrack_connect_package .../ftrack/3.3.31/connect/0.5.0/centos-6_x86-64 .../ftrack/3.3.31/connect/0.5.0/centos-6_x86-64/ftrack_connect_package.zip .../ftrack/3.3.31/connect/0.5.0/centos-6_x86-64/library.zip .../ftrack/3.3.31/connect/0.5.0/centos-6_x86-64/
Hi I'm trying to build tools that work around the context given in a certain application, such as nuke. The Issue that I have is that the current connect launch application actions don't provide a consistent context environment. For example nuke and maya, provides FTRACK_TASKID, FTRACK_SHOTID among other keys (I would consider not context based). But Nuke Studio doesn't provide any keys that are context based. It seems connect actions are designed to only provide the information that they feel is applicable to the ftrack tools running in the application, and with no c