Donal McMullan Posted March 9, 2023 Report Share Posted March 9, 2023 When I first launch Nuke in a shot context from Ftrack (via Connect), the first thing I assume I should do is save the workfile to the correct location in the project directory structure - perhaps to a 'work' directory in the shot, but I don't see anything in the Ftrack menu that would help me to do this. Have I misunderstood the Ftrack workflow? Where should my Nuke workfile be saved until I'm ready to publish it? Thanks! DJM Link to comment Share on other sites More sharing options...
Daniel Harvey Posted March 13, 2023 Report Share Posted March 13, 2023 Hi Donal, Your Nuke file should be saved locally and then Published. Steps shown in attached video; 1. Configure storage scenario to set central storage location 2. Launch Nuke from Task context, Save Nuke project locally 3. Publish Nuke project from ftrack toolbar Best, Dan Video Detail Link to comment Share on other sites More sharing options...
Donal McMullan Posted March 13, 2023 Author Report Share Posted March 13, 2023 Hey Dan - thanks for your reply and suggestion. It sounds as though ftrack's pipeline integration doesn't take an interest in workfiles, and only gets involved at publish time. Thanks again DJM Link to comment Share on other sites More sharing options...
Daniel Harvey Posted March 13, 2023 Report Share Posted March 13, 2023 Donal, That's correct. When a file is Published, either through ftrack Connect UI or an integration, it becomes a Version, which is linked to a task, tracked and can be iterated on. Best, Dan Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now