Lorenzo Angeli

Download 0.0.1 Requirement Accessible Helix Server What to expect to work Storage setup User preferences setup Publish Versioning Aim for testing Publish from any application Import/Update version through connect's asset management system Known Issues and limitations None known atm

Welcome to the new integration forum for the Perforce plugin! This new plugin provides a seamless integration with Perforce Helix Core in the form of a new storage scenario, allowing artists to publish and retrieve versions straight from it. The new integration is packaged as a native ftrack plugin, ready to be dropped in to place. This forum will have a new thread published for each release and provide a download link for each build. You can subscribe to this forum section to receive a notification when a new build is added. We recommend you use the latest build when available. Install To install, download the zipped file from the correct version and follow these instructions to get to the plugin folder, then decompress the zip in there. Build If you want to build from sources, clone the correct branch and run python setup.py build_plugin Bug report When reporting bugs to support, please remember to include: Log file Plugin version Connect version Any stack trace or error you are receiving.

Download ftrack-connect-package 1.1.1 Windows Linux Osx What's new ? This patch version aims to provide latest and greatest api , as well as a minor (linux only) improvement to provide system launcher for connect package as well as the latest version of ftrack connect nuke studio and latest python api. Changes: ftrack-connect-nuke-studio 2.2.0 Extend context template to support episodes Support for multi-track export. Fix Hiero template parser. Nuke studio now requires a context (project) to start from ftrack-connect 1.1.7 Added button in About dialog to create a Linux desktop entry file to make Connect appear in the applications menu. ftrack-python-api 1.8.0 Event description component-removed report component-added event signature. Add new scalar type `object` to factory. Add support for list of `computed` attributes as part of schema definition. A computed attribute is derived on the server side, and can be time dependentant and differ between users. As such a computed attribute is not suitable for long term encoding and will not be encoded with the `persisted_only` stragey. The `delayed_job` method has been deprecated in favour of a direct `Session.call`. See :ref:`example/sync_with_ldap` for example usage. Private method :meth:`Session._call` has been converted to a public method, :meth:`Session.call`. The private method will continue to work, but a pending deprecation warning will be issued when used. The private method will be removed entirely in version 2.0. Event server connection error is too generic, the actual error is now reported to users. Known issue None reported atm Edited January 4 by Lorenzo Angeli update download links

Download 2.2.0 What's new Change: Application requires project context to start Add: Context template update for Episodes support 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

Download 2.1.3 What's new Improve errors and bug reporting Fix EDL publisher produces multiple empty components. 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

Hi @Larissa Joos, some conventions are needed to keep data consist and simplify the logic in the applications. 3 dotted names are commonly referred to file sequences as : <prefix>.<index>.<postfix> and connect handles them as such. Would changing from dots to something different like underscores ( 1_2_3 )help in your case ? Cheers. L.

Hi @Jamie Kenyon, the easier way would be to use the ftrack-python-api directly rather than the connector ones, which really have not been built for this purpose, that said though, this is some basic code you can start playing with : please also note, connector is built on top of the legacy api and not the latest ftrack-python-api , hence you might have to do some dance to convert data between one another. Is not hard, just inefficient. from ftrack_connect_maya.connector.mayaassets import SceneAsset from ftrack_connect.connector.base import FTAssetObject scene_asset = SceneAsset() iAObj = FTAssetObject( filePath=path, componentName=componentName, componentId=newComponent.getId(), assetVersionId=newftrackAssetVersion.getId() ) scene_asset.publishAsset(iAObj) Hope it helps. L.

Hi @lloydwood, please note that does not have to be used in this way, you are free to model your assets hierarchy as you prefer. The above example is only to show one way of modelling a complex assets to take advantage of the various entity types we mentioned. Cheers. L.

Hi @lloydwood, bear with me as I'm not really sure I'm following. You are working on a Character (asset build, type Character) named TestCharacter built off different tasks (Modeling and Rigging), and publishing the model (Asset Type: Geo) and The rig (Asset Type: Rig) as whole as main component to their relative tasks. Each one of the components published on task will be versioned separately. Seem quite correct to me as overall workflow, as this will allow to keep track of your model and your rig with their own versions. Now, let's try to play with a bigger asset and see how they could be used.... Folder: Assets AssetBuild: Bumblebee Task: Modeling Asset: Head (type: Geo) Version: 1 Component: Cables, Component: Shell Version: 2 Component: Cables, Component: Shell Asset: Arm (type: Geo) Version: 1 Component: Cables Component: Shell Task: Rig Asset: Main (type: Rig) Version: 1 Component : Main (here we rig all the assets and their components, based on the latest modeling assets and components versions) Of course, this is a way of using it, but hope it helps a bit how you can use each and every bit you can publish and version. If is not clear or is not what where you are after, just let me know! Cheers. L.

Hi @Jamie Kenyon, by "ftrack menu in Maya" I suppose you mean the one on the top bar of the application. If so , here is where it gets build. With something along these lines, you should be able to add sub menus. Hope it helps ! L.

Hi @Jamie Kenyon, glad to hear ! If there's anything else you know let us know . Cheers. L.

Hi @Jamie Kenyon, that's strange, you can see a fully working example here : https://bitbucket.org/ftrack/ftrack-connect-houdini/src/588f93210b9d5a65307a5eee6900d861d3ff1fe6/resource/hook/ftrack_connect_houdini_hook.py#lines-109 If still does not work would you be able to send your application launcher either here or sending it at support@ftrack.com so we can have a closer look ? Cheers. L.

Hi @Mike, virtual environment are made so whatever you do install in there (python module wise) will remain sandboxed and won't affect the system. If you want to use Lucidity I'd suggest to create a virtualenv , activate it, and install the modules you need in there. Once done , you can use an event like the one I posted to extend the PYTHONPATH including the one in the virtualenv to make them pick up. Hope it helps! L.

Hi @Jamie Kenyon icon should be a full web address where to pick the icon from, cannot be (atm) a local path, Try setting this path and see whether does work: "https://image.flaticon.com/icons/png/512/33/33447.png" hope it helps. L.

Hi @Mike, although totally doable, rather than modifying the original maya hook I'd suggest to provide a separate event in your central or local FTRACK_CONNECT_PLUGIN_PATH such as this one that modifies the env at startup time. import os import ftrack import ftrack_connect.application python_dependencies = 'path to your modules' maya_script_path = 'path to maya python scripts' def on_application_launch(event): '''Handle application launch and add environment to *event*.''' ftrack_connect.application.appendPath( python_dependencies, 'PYTHONPATH', event['data']['options']['env'] ) ftrack_connect.application.appendPath( maya_script_path, 'PYTHONPATH', event['data']['options']['env'] ) def register(registry): '''Subscribe to application launch events on *registry*.''' if registry is not ftrack.EVENT_HANDLERS: return ftrack.EVENT_HUB.subscribe( 'topic=ftrack.connect.application.launch and data.application.identifier=maya*', on_application_launch ) For what concerns Lucidity, this module has been removed from ftrack connect package from verion 1.0.0 on: https://bitbucket.org/ftrack/ftrack-connect-package/raw/09a31db1cba8586fa129d3fb64d91fec38d32dca/doc/release.rst I'd suggest to install separately and provide it through the above system if you need it. Hope it helps. L.