Forums
-
Company news
-
- 12
- posts
-
-
ftrack Studio (main app)
-
- 1,076
- posts
-
- 1,150
- posts
-
- 1,418
- posts
-
- 550
- posts
-
- 234
- posts
-
- 19
- posts
-
-
ftrack Review
-
- 94
- posts
-
- link to session
- By TTT,
-
- 102
- posts
-
- 26
- posts
-
-
Connect and plugins
-
- 345
- posts
-
- 7
- posts
-
- 144
- posts
-
- 289
- posts
-
- 15
- posts
-
- 2.2.1
- By Lorenzo Angeli,
-
-
Tech preview
-
- 1
- post
-
- 30
- posts
-
- 0.1.0
- By Lorenzo Angeli,
-
- 31
- posts
-
- 3
- posts
-
-
Popular Contributors
Nobody has received reputation this week.
-
Status
-
Who's Online (See full list)
There are no registered users currently online
-
Recent posts
-
-
By Lorenzo Angeli · Posted
Hi @TTT there's no need to install it locally to each machine. This event can be easily hosted on a central network folder and mapped into the FTRACK_CONNECT_PLUGIN_PATH Hope it helps. L. -
By Lorenzo Angeli · Posted
Hi @John Su, the path is resolved through an event available in ftrack_connect itself and called resolve.py If the path is red is possible that your structure cannot be properly initialised and hence not be resolved. You can try adding more logs into the resolve.py and see if anything is off. Please send us , either here or through support (depending on how sensible the information are) and we'll look further into it. Hope it helps. Cheers. L. -
It's worth mentioning that the path is 100% available by "location.get_component_availability()" even though it's red.
-