Daniel Harvey

Hi Marcus, I've tested this with ACES OCIO config and have noticed that selecting ‘None’ for any Transform (not just Look) once it has been populated does not clear the previously selected Transform (screen recording of behaviour here) Can you confirm this behaviour with other Transforms (eg, input) in your case? Best, Dan

Fernando, 'Done' tasks are not displayed in the Timesheet but you can log time on 'Done' tasks from the sidebar as shown in the screenshot Best, Dan

Fernando, If you filter as shown in the screenshot this should resolve any ambiguity in time calculations Best, Dan

Hi Fernando, I've raised a ticket for this issue for the visibility of our support team. Best, Dan

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

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

As you have noted, default behaviour in the ftrack UI is to name folders according to project structure, eg, <project name>/<object name>/<asset name>/<version name>/ This can be customised with a location plugin if you want to assign folder / filenames explicitly when publishing via ftrack Connect Introduction to creating location plugins here http://ftrack-connect.rtd.ftrack.com/en/stable/developing/tutorial/adding_a_location.html