Jump to content

Search the Community

Showing results for tags 'Environment'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Company news
    • General announcements
  • ftrack Studio (main app)
    • General discussion
    • Feature requests
    • API
    • Help
    • Actions and Widgets
    • ftrack Go
  • ftrack Review
    • General discussion
    • Feature requests
    • Help
  • Connect and plugins
    • General discussion
    • Connect package releases
    • Feature requests
    • Help
    • Connect plugins releases
  • Advisory Forum
  • Tech preview
    • API
    • New integrations
    • Studio overview
    • ftrack Review

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 3 results

  1. 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
  2. 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/
  3. 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
×
×
  • Create New...