Jump to content

Lorenzo Angeli

Administrators
  • Content Count

    229
  • Joined

  • Last visited

  • Days Won

    16

Posts posted by Lorenzo Angeli

  1. Download 0.3.1
    Originally written by Mike Datsik

    What's new

    * Changed Update setup process
    * Fixed: Houdini fails to load under linux
     

    How to install

    stop ftrack-connect-package

    download and uncompress the new version in :
    <ftrack-connect-package>/resource/connect-standard-plugins/ 
    restart ftrack-connect-package

  2. hi @matthieu, 

    we are actively working on connect for python on 3 .If you like to give it a go , you can try this branch
    This new version though is not compatible with the current integrations ., but we are working on solutions to make them work back, just not there yet.

    In regard of your error, seems strange to be coming from the api , as it seems to be referring to Dialogs, which are just a ui thing.

    There'll be some news soon.
    Cheers.
    L.

     

  3. Download 1.3.0

    Changes:

    Changed : Update pyside signal signature for pyside2 compatibility.
    New : Add support for FBX import.

    1) remove previous plugin from either connect plugins or connect resources.
    2) download the new version from the above link
    2) decompress the zip in the FTRACK_CONNECT_PLUGIN_PATH
    3) restart connect

    If there's any problem please let us know!
    L.

  4. Download new hook file.

    The installation directories for Cinema 4D have changed with the recent releases.
    In order to show the new applications, you must replace the existing hook file, which can be found in the following directories:

    macOS:
    /Applications/ftrack-connect.app/Contents/MacOS/resource/hook

    Windows:
    C:\Program Files (x86)\ftrack-connect-package-1.1.1\resource\hook
     

  5. Download 2.4.1

    What's new

    • New :    Startup error related to location setup are now visually reported.
    • Fixed :   Discovery does break on non context entities.


    How to install

    • stop ftrack-connect-package
    • remove previous nuke studio plugin from : 
    • <ftrack-connect-package>/resource/connect-standard-plugins/ 
    • download and uncompress the new version in :
    • <ftrack-connect-package>/resource/connect-standard-plugins/ 
    • restart ftrack-connect-package
  6. Download 0.3.0
    Originally written by Mike Datsik

    What's new

    * Changed Add file logger
    * Changed Update pyside signal signature for pyside2 compability.
    * New : FBX export on publish.
    * New: FBX import.
    * Fixed: Thumbnail save failed on windows publish.
    * Changed: Have plug-in load proceed if there is an exception setting up frame range and fps.
    * Fixed: Hip can now be imported on Windows with paths having backlash (\) elements.
    * New: New Import,Merge & Open import options.

    How to install

    stop ftrack-connect-package

    download and uncompress the new version in :
    <ftrack-connect-package>/resource/connect-standard-plugins/ 
    restart ftrack-connect-package

  7. Hi @Aaron Powell, more than "whatever works for you" is really the fact we try not to enforce these , as are usually defined by studio structures and pipelines.
    that said, it really depends on what you are after..... overall if you just have scripts which use the ftrack_python_api, my suggestion would be to have them stored in a central place and mapped to the PYTHONPATH (you can think also to have some inheriting from a central path for utilities and having modules named for each show with the specific code you need.)

    On how, you can go from setting PYTHONPATH into the envs to use something like REZ to handle it all from there.
    The latter option could be a bit of a stretch , depending on how often you need to maintain these, but might worth the time.

    Hope it helps.
    L

  8. Hi @John, sorry for the delay on getting back to you.
    if you have a centralised storage scenario, the easier one would be to provide your own custom location , having it registered and then through an action provide the transfer of the components into the other location.
    The only thing you need to be careful about are the priorities of the location themselves, so you don't (by mistake) make the other one replacing (as priority) the centralised storage.

    here couple of examples might be of help in your journey :)

    https://bitbucket.org/ftrack/ftrack-recipes/src/master/python/actions/multi_site_location/
    https://bitbucket.org/ftrack/ftrack-recipes/src/master/python/actions/migrate_components/

    I'd suggest looking into these while keeping at hand the documentation for the location/structure system.

    http://ftrack-python-api.rtd.ftrack.com/en/stable/locations/tutorial.html?highlight=location
    https://help.ftrack.com/en/articles/1040442-locations

    Hope it helps.
    L.

     

  9. Hi @zhouyu08512, sorry for the delay on getting back to you.
    Versioning is handled by ftrack itself and is not something we allow to define though the Nuke Studio templated names.
    I'd suggest, if you haven't yet, trying the latest version available on the forum  and see whether the video issue is solved.

    let us know how it goes.

    If the problem persist, please open a ticket with support@ftrack.com so we can properly investigate your issue.
    Cheers.
    L.
     

  10. All platforms:  Download 1.0.3

    Documentation
     
    Changes since last version

    • fixed : Action icons not correctly loading.
    • changed: Version comments are published as Perforce changelist description.
    • new : Update docs to include timeout solution for credentials.

     

    How to install

    • stop ftrack-connect-package
    • remove previous nuke studio plugin from : <ftrack-connect-package>/resource/connect-standard-plugins/ 
    • download and uncompress the new version in :<ftrack-connect-package>/resource/connect-standard-plugins/ 
    • restart ftrack-connect-package
  11. Hi @Rory , as long as the module you are importing are in PYTHONPATH it should work. 
    If you have both python2 and 3 available be careful though as the variable is the same for both and can lead to issues.
    If you still have issues, please send the relevant code to our support providing details about where the third party module is located and how has it been installed.
    Cheers.
    L.

×
×
  • Create New...