1. Company news

    1. 19
      posts
  2. ftrack Studio (main app)

    1. 1,201
      posts
    2. 1,219
      posts
    3. API

      1,701
      posts
    4. 622
      posts
    5. Actions and Widgets

      Extending the functionality in ftrack with custom Actions and Widgets - read more at ftrack.com/actions

      276
      posts
    6. ftrack Go

      Discussions about ftrack Go for iOS and Android

      28
      posts
  3. ftrack Review

    1. 98
      posts
    2. 112
      posts
    3. 26
      posts
  4. Connect and plugins

    1. 388
      posts
    2. Connect package releases

      Notes on the latest Connect releases.

      7
      posts
    3. 146
      posts
    4. 312
      posts
    5. 48
      posts
  5. Tech preview

    1. API

      18
      posts
    2. New integrations

      Discussions of the new tools that will replace current Connect integrations into Nuke, Maya, 3DS Max and other applications.

      31
      posts
    3. 31
      posts
    4. 3
      posts
  • Popular Contributors

  • Status

  • Who's Online (See full list)

    There are no registered users currently online

  • Recent posts

    • Sorry for the confusion I caused, Jed. The review functionality should be quite mobile friendly; that is to say for ftrack Review and the external review sessions for ftrack Studio. I hope that helps.
    • Hi, I'm currently testing ftrack to see if I can integrate it into my workflow. Sadly, the issue I have is that ftrack-connect doesn't seem to be working with Python3 (which is what I have been using to make my tools in blender and Houdini) When I'm launching houdini from ftrack-launcher, I don't have access to 'Import Asset' tool, or anything related to ftrack. I also tried to import the ftrack_api to see if that was working but it's not neither. I got this message: File "<stdin>", line 1, in <module> AttributeError: module '__main__' has no attribute 'FtrackDialogs' Is there any plan to upgrade it to python3 so we can use it with python3 build of for example Houdini18.5 ?
    • As a user I would disagree with this. It may be OK on an ipad, but since there don't seem to any concessions to the smaller screen size it is pretty difficult to use on a phone.
    • Hi John, This feature request is still active and send to the development team for future updates. I can't give an ETA but I will update the request and make sure the development team is aware that this is still a wanted feature for an upcoming update. Regards Simon