Lorenzo Angeli

Hi @Bruce you can find the connect logs in the following locations : Windows: C:\Documents and Settings\<User>\Application Data\Local Settings\ftrack\ftrack-connect\log macOS: ~/Library/Application Support/ftrack/ftrack-connect/log Linux: ~/.local/share/ftrack-connect/log you can find more information about connect on our help if you need. Cheers. L.

@Bruce could you please open a ticket with our support and provide the connect's log files so we can have a closer look ? Thanks. L.

Hi @Bruce osx is a bit trickier for environment variables to setup, but the following should work. (please note I'm not an osx user myself so I had to rely on some company hive mind for the following) 1) check the current shell in use with : 2) depending on your shell in use edit bash or zsh profiles: you can append the export command to the .bash_profile or .zshrc file. Open Terminal and type : or you can then add the environment variables in this file as: Once done save and quit. If you want to load the environment variables rigth away just source the file with : or Hope it helps ! let us know. Cheers.

Hi @Bruce I have tested the user location just yesterday on latest connect and seems to be working fine. From the error it seems you are having issue on the environment variables setup, may I ask on what Os are you using it ? if you are on OSX you might have different options to do so depending on the shell type in use.

Done @Joel Hutton

@Bruce please open a ticket with support@ftrack.com and we'll pick it up from there, Cheers.

Hi @MeadowEstrada , the information you are after I believe are under the various TypedContext entities. maybe this action example can help you out. let us know ! Cheers. L.

Hi @dima, both ftrack-sftp-accessor and ftrack-s3-accessor are api plugins and not server ones, therefore there's no point in trying to have them installed on the self hosted server. In each repository you can find a snippet on how to initialise and use them just through the api: s3-example , sftp-example You can find an example use of the s3-accessor in this user-location plugin for your third point, there's no need of using lambdas , you can just rely on the internal ftrack events to do so, please check the user-location above as reference. hope it helps/ L.

Hi @dima if you are just starting with the Location system, I'd suggest having a look at our location webinar. If you are after some more technical details have a look at our documentation and our recipes repository. Please start using this as plugin , following the example from the recipes. Hope ithelps. L.

Hi @Omar Wanis you are right, curently Ftrack Connect does not take in account the version embedded in the filename. I'll raise it with the correct team to see whether is something to be added in a future version, cheers!

@andrewb invite sent !

Hi @Andriy Pogribniy ftrack supports any number of locations a the same time but locations by default do not contain any logic on what goes where ,unless you customise the location itself or the tool that uses them as described above. The session by default will pick up the one with higher priority and use that but you can always change (when using api) the destination location at publish time without any problem. You can find more information on how location works also in the api documentation. Hope it helps. L.

Hi @Andriy Pogribniy glad to hear is working. If you have doubts on how location works I'd suggest having a look at our webinar on the subject. you can also find example locations on our recipes . Documentation wise, we are on it ! Hope it helps. L.

Hi @Andriy Pogribniy There are various way you can archive this . The first is to write what I'd call a proxy location. Such an object would have as input a set of destination locations and the methods such as add_component, remove_component , get_component_availability, etc... would contain the logic to define where the data would be saved depending on the rules you decide. Another option would be to customise connect publisher widget to allow a location selector. if you want to take inspiration , there's an old PR on bitbucket which implements it, but should be ported over the new publisher plugin. https://bitbucket.org/ftrack/ftrack-connect/pull-requests/281 hope it helps. L.

Hi @Nikolay Skolkov Could you give us some more information on how you are publishing USD and from which application and to what entity type ? Are you currently using any of the integration or from the api ? Could you describe what you are after in details ? Thanks ! L. p.s Feel free to file a ticket with support with all the information if you prefer.

Hi @SteveZeelo yes that should work. Please evaluate the option to of setting the env as $FTRACK_CONNECT_PLUGIN_PATH;<YOUR PATH> this way you won't override but extend allowing a higher degree of customization. Hope it helps. L.

@Andriy Pogribniy you can , and to simplify the process you can make use of the ftrack-action-handler module (available on pip). Please have a close look at the AdvancedBaseAction and let us know if you have any issue. Hope it helps. L.

@Nikolay Skolkov the code you have provided is just the location creation, and is lacking of the other registration part , which is hooked to the application (DCC) or connect action startup. Please have a look at this example location which does it using two separate scripts: 1) the hook which set the environment variables and register the location 2) the actual location code You can also use one single function do to it all as by this other example. Hope it helps. L.

Hi @Nikolay Skolkov can you please share the full code of your location so i can have a look ? if you prefer, you can send us a support ticket and we'll reply from there. Cheers. L.

Hi @Nikolay Skolkov it does make sense the behaviour you are seeying as you need to have the location registered when the application start. Please have a look at this custom location for the other events you want to subscribe to. namely : * 'topic=ftrack.connect.application.launch' * 'topic=ftrack.action.launch' This is because when application starts all the environment variables are reset to ensure the application start from a clean slate and these events, re inject the modules in the application. hope it helps.

Hi @Nikolay Skolkov assuming your code is reacheable by PYTHONPATH and FTRACK_EVENT_PLUGIN_PATH (or installed as plugin in connect as by our example) and the storage scenario is disabled, you can ensure the location is properly setup calling from api : session.pick_location() if this returns a location entity , you can then check whether the location.accessor and location.structure points are not set to None. Note the transfer component is a separate code from the Location itself , you can find it as part of another example. You can find more information on how location works on our api documentation. Hope it helps. Cheers. L.

That's I believe is done in the Location structure plugin itself.

Hi @Nikolay Skolkov The script which resolves the path lives in ftrack-connect under hooks with the name of resolver.py. That said, all the script does is to query the location for the resource identifier and use that. You could try to modify the resolver and relace the \ with / depending on the OS which triggers it. Hope it helps. L. P.s For windows mountpoints I usually suggest to set an actual mount on the machine such as G://projects as it cause less issues.

Hi @Brian, I see what you mean. Please have a look here to see how the ftrack-action-handler implements a robust solution. Hope it helps. L.

Hi @maudeads , sorry to hear you also been been having issues. Please feel free to tell us what you found tricky to setup ! Cheers. L.